|
|
Hi YK, We already dwnload ATV12 SDK from Amlogic. It is ok to run on AML reference board. Porting to Eagle board will be started from 9/5. The plan for next week is: 1. HW GPIO pin config and 3GB Ram config 2. IR key mapping 3. eMMC partitions Thank you ! |
|
|
Hi Kerwin Thank you for the update And SKB created a project in bitbucket. + bitbucket : https://bitbucket.skbroadband.com/projects/FSTB-12 + project name : STB_DEV_F-STB-12 + project key : FSTB-12 Please don't commit the AMLOGIC SDK to the bitbucket yet There is a Amlogic common repository issue between Amlogic and SKB. I will tell you how to commit after the issue is resolved. Thank you! YK.Jung |
|
|
Hi Kerwin This meeting has been rescheduled for Monday afternoon / Wednesday afternoon. And I have to report the progress of FXN to SKB at every meeting. so please briefly comment on the progress every Monday and Wednesday before lunch. And , I am talking to SKB based on the schedule that Jacky sent me before. Attached capture file - if there is any significant change in the schedule, please let me know. - Jira for each WBS item will also be created. Thank you YK.Jung OS12_schedule.PNG (27,777 bytes) |
|
|
Hi Kerwin I have an OS12 upgrade meeting this afternoon. Please let me know the progress. And please let me know if you have any questions or requests Thank you YK.Jung |
|
|
Hi YK, updates on 9/07 1. HW GPIO pin config and 3GB Ram config ==> boot successfully with 3GB RAM config on eagle non-secure board. Now, we are working on pin configurations in kernel |
|
|
Hi Kerwin Please commit the pure ATV12 SDK to FXN bitbucket , ( and please commit the things that have been fixed so far ) + bitbucket : https://bitbucket.skbroadband.com/projects/FSTB-12 + project name : STB_DEV_F-STB-12 + project key : FSTB-12 And please let me know after commit , then I will check it There is no meeting next Monday(Sep/12th) because it is "Korean thanksgiving day". I will ask you again about the progress next Wednesday(Sep/14th) Additionally, the project schedule was converted to a date and placed in confluence. https://confluence.skbroadband.com/pages/viewpage.action?pageId=294983188 This schedule will be shared with the SKB PM. Thank you YK.Jung |
|
|
Hi YK, It will be faster if AML push common SDK to BitBucket first. Could you help to discuss this with AML and SKB ? Thank you ! |
|
|
Hi Kerwin The BitBucket issue is still under discussion and I will let you know when the content is updated. And I have an ATV OS12 upgrade meeting this afternoon. Please let me know the progress. Thank you YK.Jung |
|
|
Hi YK, Update status for OS12 upgrade: 1. HW GPIO pin config and 3GB Ram config => Done 2. IR key mapping (basic DPAD control) => Done 3. External Ethernet Phy. (realtek) => Done 4. USB host/device support => Done 5. eMMC partitions => In progress Please help to discuss with SKB/SPTEK for issues below: 1. USB WiFi dongle for Google certification (https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1537 ) 2. For IR/BT key mappings, we can't put BA01/BA02 key layout files now because there are special keys defined by MW. (SKB_FUNC_xx) Please check with SPTEK if there is a patch or not. Thank you ~ |
|
|
Hi YK, Update status for OS12 upgrade: eMMC partitions => In progress, there is a guide from AML for Q to S partition and OTA, still study it. BT => BT function works well, there is no problem to pair BA01/BA02 in Android Setting UI. But there is the same issue as IR key mapping. We can't put SKB function keys in key layout files. We plan to integrate secure build as next target. Thank you ! |
|
|
Hi Kerwin Thank you for the update. Regarding Key layout, I have already reported it to SKB/SPTEK. SPTEK says it can be provided after ATV12 FXN bitbucket is completed I will update you after the meeting this afternoon. Thank you !! YK.Jung |
|
|
Hi Kerwin SKB and INTEK uploaded the Amlogic AT12 Common SDK to bitbucket. Based on this, please setup FXN bitbucket environment. ====== Amlogic ATV12 common SDK ============= mkdir s-amlogic-gtvs-aml cd s-amlogic-gtvs-aml repo init -u ssh://git@bitbucket.skbroadband.com:7999/amandroids/manifests.git -b AML_ATV_Q2S repo sync --force-sync --force-remove-dirty -c repo start AML_ATV_Q2S --all ==================================== < FXN bitbucket path > + bitbucket : https://bitbucket.skbroadband.com/projects/FSTB-12 + project name : STB_DEV_F-STB-12 + project key : FSTB-12 How long does it take to setup a FXN bitbucket environment? Thank you YK.Jung |
|
|
Hi Kerwin I have an ATV OS12 upgrade meeting, please let me know the progress. And how long does it take to setup a FXN bitbucket environment? Thank you YK.Jung |
|
|
Hi YK, We are preparing BitBucket environment now. AML common SDK on BitBucket is downloaded, we are checking to use upload or fork for FXN BitBucket path. It may be done by tomorrow (9/22). After FXN BitBucket is done, we will check commit history on Android 10 and assign owner to finish porting. BTW, eMMC partition and secure boot build is still in progress. Thank you ! |
|
|
Hi Kerwin The bitbucket build environment and minimum behavior on BFX-AT100 must be shared quickly. The reason, SPTEK is currently unable to start working on bitbucket(FSTB-12) (SPTEK confirmed the recovery mode operation on INTEK and Innopia ATV12) Please let me know when SPTEK will be able to start working on FXN bitbucket. And can the eMMC partition work be completed by this week? Thank you YK.Jung |
|
|
Hi YK, We have push SDK to BitBucket, please check if SPTEK can get it or not. We will push current modifications on 9/26. Thank you ! |
|
|
Sorry I forgot to update, the original SDK upload is finished, here's the URL: repo init -u ssh://git@bitbucket.skbroadband.com:7999/fstb-12/manifests.git -b AML_ATV_Q2S |
|
|
the commits for eagle board have been verified and push to branch BFX-AT100_5.3.4 please note currently only non-secure board supported. here's the URL: repo init -u ssh://git@bitbucket.skbroadband.com:7999/FSTB-12/manifests.git -b BFX-AT100_5.3.4 |
|
|
Hi YK, Update current status for ATV12 porting 1. FXN bitbucket Environment: done, SPTEK and pull and build FW for non-secure boot Smart3 boards. 2. eMMC partition: partition table is done, still change script to mount btv_home for BTV framework 3. commit list for ATV12 porting: We make a diff between Amlogic command SDK and BFX-AT100_5.3.4_r18. There are about 4520 commits and we are still reviewing the list to exclude unnecessary patch (security patches, google framework updates..etc) . Now, the total number is 2423. Thank you ! |
|
|
Hi Kerwin This Wednesday's meeting(SEP/28th) has been changed to Thursday(SEP/29) Please update the progress by Thursday afternoon. Additionally, I tried to build the code in FXN bitbucket. but error is occurring. Is there no problem with the build when using the FXN bitbucket code ( branch BFX-AT100_5.3.4) ? I used "./release.sh" for compile ./release.sh ======> start build with params: model=BFX-AT100 submodel=NA variant=userdebug fxtype=NA ota=y secure=n avb= And confluence and jira created are as follows. 1) AML ATV OS 12 release_note ( AML will be updated here in the future. ) https://confluence.skbroadband.com/display/BTFAML/1.+Release+notes+for+Android+S 2) Created a Jira Project for ATV OS 12 FXN JIRA project : https://jira.skbroadband.com/projects/FSTB12 AML JIRA project : https://jira.skbroadband.com/projects/AMANDROIDS Thank you YK.Jung |
|
|
Hi Kerwin / Jim SKB manager decided to integrate branch name + ALT(Foxconn) Smart3(BFX-AT100) : BFX-AT100_5.3.4_S_DEV + Intek Smart3(BID-AT200) : BID-AT200_5.3.4_S_DEV + Innopia Smart3mini(BIP-UW200) : BIP-UW200_5.3.4_S_DEV Please change the workspace from BFX-AT100_5.3.4 to BFX-AT100_5.3.4_S_DEV. That is, please create the BFX-AT100_5.3.4_S_DEV branch and proceed here. Thank you YK.Jung |
|
|
Hi YK, OTA is not verified yet, so current "release.sh" doesn't support to build OTA archive. Please set "build ota file?" as 'N' Thank you ! |
|
|
update URL: repo init -u ssh://git@bitbucket.skbroadband.com:7999/FSTB-12/manifests.git -b BFX-AT100_5.3.4_S_DEV |
|
|
Hi Kerwin When SPTEK attempts to verify recovery function, an OTA image must be created. Please assign a priority to the OTA package work at "./release.sh" , { "build ota file?" Y } Thank you!! YK.Jung |
|
|
Hi Kerwin Please update the progress Thank you !! |
|
|
Hi YK, Update current status for ATV12 porting 1. Integrate AML signed tool for secure boot boards ==> signed image is verified OK on secure boot board. Need to integrate with 'release.sh' script. 2. eMMC partition and OTA ==> Solve build errors and boot up fail issue for btv_home folder 3. Review commit list for ATV12 porting ==> in progress Thank you ! |
|
|
Hi Kerwin INTEK is currently working on the Provisioning Key for ATV OS 12. I have one question The FXN was using a unified key at OS 9 / 10, as a result, some error messages have been observed https://jira.skbroadband.com/browse/BTFAML-754 [ 8.288017] [TEE] [HDCP-TA] hdcp_load_key: read hdcp key(hdcp_tx22.bin) ret = 0xFFFF0008 [ 8.288021] [TEE] [HDCP-TA] hdcp_load_key: read hdcp key(hdcp_tx14.bin) ret = 0xFFFF0008 [ 8.288023] [TEE] [HDCP-TA] hdcp_load_key: read hdcp key(hdcp_rx14.bin) ret = 0xFFFF0008 https://jira.skbroadband.com/browse/BTFAML-550 02-01 09:55:06.179 6236 6310 W System.err: android.media.NotProvisionedException: Failed to open session 02-01 09:55:06.179 6236 6310 W System.err: at android.media.MediaDrm.openSession(Native Method) 02-01 09:55:06.179 6236 6310 W System.err: at android.media.MediaDrm.openSession(MediaDrm.java:888) etc... ... In fact, no one is guaranteeing that the above error message is not an issue. Therefore, I think it will be helpful to proceed with the work if the above message is not visible. Then, is the provisioning key method used in ATV OS 12 this time? Thank you YK.Jung |
|
|
Hi YK, Provisioning key should not be used on BFX-AT100/BFX-UH200 models for ATV12. There are a lots of Smart3 board using unified key since ATV 9. We don't have a method to remotely write provisioning keys to the boards on field. This is why we keep to use unified keys for ATV10 and ATV12. Thank you. |
|
|
Hi Kerwin I see, I understand that Smart3 ATV12 does not use provisioning key. And when will the OTA option be available at ./release.sh ? { "build ota file?" Y } And when I compile with the release.sh file, I can see that something is cleaned and then compiled again. Please review again to see if there are any problems with the release.sh file. Thank you!! YK.Jung |
|
|
Hi YK, Please tell SPTEK to check "frameworks/native/include/android/keycodes.h" There is a build error after the patch. Thank you ! BFX-AT100_5.3.4_S_DEV_build_error.png (60,404 bytes) |
|
|
Hi Kerwin I reported this build error to SPTEK. SPTEK will push later. First, please insert , in the keycode.h file for compile and proceed. AKEYCODE_PROFILE_SWITCH = 288 to AKEYCODE_PROFILE_SWITCH = 288, Thank you YK.Jung keycode_compileError.png (27,877 bytes) |
|
|
Hi YK, There is still compile error after adding new key definitions. Please check it with SPTEK. Thank you ! atv12_new_key_error.png (60,785 bytes) |
|
|
Hi YK, Update current status for ATV12 porting 1. Integrate AML signed tool for secure boot boards * signed image is verified OK on secure boot board. Need to integrate with 'release.sh' script. ==> Done 2. eMMC partition and OTA * Solve build errors and boot up fail issue for btv_home folder ==> Done * OTA from ATV12 to ATV12 ==> OK * Checking upgrade failed from ATV10 to ATV12 3. Review commit list for ATV12 porting ==> in progress Thank you ! |
|
|
Hi Kerwin Thank you for updating the progress. I will request SPTEK again about compilation error Thank you!! |
|
|
HI Kerwin SPTEK says the compilation error has been fixed. please check it And, SPTEK tested the upgrade with the update.zip file generated with the ./release.sh file. However, update failure is occurring at recovery 24% ( OTA fail from ATV12 to ATV12 at Non-secured board ) Please check it ==================================== SPTEK's log ============================================================== [ 10.239184] copypath[/tmp/sideload/package.zip] update_file_path[/tmp/sideload/package.zip] mUpdatePackage[/tmp/sideload/package.zip] [ 10.272464] runUpgrade : USB_UPGRADE_MODE [ 10.639465] Finding update package... [ 10.639517] Opening update package... [ 10.640458] Verifying update package... [ 12.090289] Update package verification took 1.4 s (result 0). [ 12.090491] fw_support_multiethernet is 0 [ 12.090650] IS RTK Board [ 12.090698] Installing update... [ 12.177481] SELinux: Loaded file_contexts [ 12.182492] mount: Failed to mount /dev/block/by-name/oem at /oem: No such file or directory [ 12.182551] script aborted: file_getprop: failed to read /oem/oem.prop ====================================================================================================== Thank you!! |
|
|
Hi Kerwin SKB is requesting if it is possible to additional free space of about 50~60Mb becuase STB is currently lacking free space. That is , SKB is asking FXN to remove unnecessary apps or libraries to free space on ATV 12 Unable to use xwalk because of /dev/ashmem access never allow on ATV12 Therefore, it need to build additional chromium/webview, so it need to additional free space. Thank you!! YK.Jung |
|
|
Hi YK, Please check replies within below: 1. OTA failed from ATV12 to ATV12 ==> Follow AML's suggestion, we remove oem partition to be compatible with ATV10. Jerry had verified for ATV12->ATV12 OTA and will commit patches to BitBucket today. 2. To have 50 ~ 60MB free space ==> Which partition need to have additional 50~60MB ? Thank you ! |
|
|
Hi Kerwin 50M~60M of the built(chromium/webview) library will be added to the system partition. So SKB is asking for the removal of unnecessary data at system partition. but I have one question I don't think there will be any problem with using any partitions because ATV12 use super partition. is it correct? And there is an ATV12 meeting today, so please update current status for ATV12 porting Thank you !! YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. eMMC partition and OTA * Commit partition related patches to BitBucket ==> Done * Work with AMLogic to check upgrade failed from ATV10 to ATV12 2. Porting and add ADC kernel driver to BitBucket ==> Done 3. Review commit list for ATV12 porting ==> in progress Thank you ! |
|
|
Hi Kerwin SKB requested a review of the downgrade function ( ATV 12 -> ATV 10 ) it's not common sense , but SKB requested that function ( Emergency Recovery) Is it possible to OTA downgrade from ATV12 to ATV 10 ? if it's impossible , please let me know the reason why it's impossible. Thank you YK.Jung |
|
|
Hi Kerwin If you do "repo sync" at BFX-AT100_5.3.4_S_DEV , you will be able to see the BTF API functions Please implement these functions. Thank you!! YK.Jung |
|
|
Hi Kerwin Next Monday(OCT/10th) is a holiday at here, so the ATV12 upgrade meeting has been canceled at DEC/10th So please update the progress on OCT/12th ( skip OCT/10th ) And please check below two items - is it possible to OTA downgrade from ATV12 to ATV10 ? - please implement BTF API functions Thank you!! YK.Jung |
|
|
Hi YK, - is it possible to OTA downgrade from ATV12 to ATV10 ? ==> We are checking the possibility for downgrade Basically, it will be blocked by build timestamp. We need to remove timestamp checking and check result. - please implement BTF API functions ==> We will discuss it internally and assign owner. Thank you ! |
|
|
Hi YK, - is it possible to OTA downgrade from ATV12 to ATV10 ? In Google original OTA build script, if you want to do OS downgrade, A data wipe will always be enforced. |
|
|
HI Jason I have two question... then. 1) Does the Google setup menu always run after the downgrade(from ATV12 to ATV10) ? 2) Do user always have to put the BTV authentication number after downgrade ( from ATV12 to ATV10 ) ? - (Is btv_home data also always erased? ) Thank you!! YK.Jung |
|
|
Hi YK, >>>1) Does the Google setup menu always run after the downgrade(from ATV12 to ATV10) ? Yes, because /data is wiped. All user data is gone. (e.g. login Google account, the application data) >>>2) Do user always have to put the BTV authentication number after downgrade ( from ATV12 to ATV10 ) ? - (Is btv_home data also always erased? ) No /btv_home is not designed by Google. OS downgrading doesn't wipe /btv_home. However, if the the data structure of /btv_home between ATV12 and ATV10 are different. I think there is a risk of boot failure after downgrading from ATV12 to ATV10. Thanks, Jason |
|
|
Hi Jason Thank you for the explanation. I will discuss this with SKB during today's ATV12 meeting. Thanks |
|
|
Hi Kerwin Please update the progress for ATV12 meeting And now SD FW is being upgraded to ND board. Please check it as well. Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. ATV10 to ATV12 OTA * Check "no command" issue (Mantis#1544) 2. Porting BTF HAL APIs * Start to check BTF HAL APIs on ATV12 3. Review commit list for ATV12 porting ==> in progress, number of commit list is reduced from 2423 to 1382 Thank you ! |
|
|
Hi Kerwin There is nothing commited to bitbucket about ATV12 OS upgrade since 10/6. Currently, in the case of INTEK, the HomeUI is running in Permissive mode and video is being played on Live channel but, AC3 codec has not yet merged in INTEK, so there is no sound at AC3 channel. Anyway, there is no progress in the FXN bitbucket right now. so SPTEK doesn't care because there's no commit content. Please commit it as soon as it is implemented. (BTF HAL.. etc.. ) Thank you!!! YK.Jung |
|
|
Hi Kerwin , Jason The ATV OS downgrade ( ATV12 -> ATV10) feature has been stopped. Please focus only on upgrading from ATV10 to ATV12 And SKB requested a review of the "Incremental update" feature in ATV12 Please give me your review comments on the "Incremental update" in ATV12. Thank you YK.Jung |
|
|
Hi YK, Here are some key points for incremental OTA 1. While release a new FW, we need to have incremental OTA files for each released FW It will take more time to release a new FW. (we have 3 type of FW, ND/SD/SU) For each FW, it will be: r1-full r2-full, r1-r2-inc r3-full, r1-r3-inc, r2-r3-inc r4-full, r1-r4-inc, r2-r4-inc, r3-r4-inc r5-full, r1-r5-inc, r2-r5-inc, r3-r5-inc, r4-r5-inc .. .. 2. OTA Server need to know which incremental OTA file should be provided for each client request. If there is no incremental OTA for the client, a full OTA file should be provided. The kind of management should be implemented by SKB OTA server. Thank you ! |
|
|
Hi YK, Update current status for ATV12 porting 1. ATV10 to ATV12 OTA * Check "no command" issue (Mantis#1544) => Done 2. Support system reset mode => Done 3. Add downgrade protection for second source board => Done 4. Porting BTF HAL APIs * porting BTF HAL APIs on ATV12, there are some compile errors on ATV12. 5. Review commit list for ATV12 porting ==> in progress, number of commit list is reduced from 1382 to 892 Thank you ! |
|
|
Hi Kerwin There were three discussions at yesterday's meeting. 1) A low power mode shall be implemented in ATV12. (Not right now, please consider it later.) 2) Free space ( https://jira.skbroadband.com/browse/FSTB12-3 ) remove unnecessary apps or libraries to free space on ATV 12 3) Implementation of BTF HAL functionality INNOPIA STB can watch the live channel now at permissive mode Only FXN ATV12 is not available for live channel. Amlogic and SPTEK are testing only with INTEK and INNOPIA models. Please implement it as soon as possible. Additionally, if you compile with the current bitbucket source and run ATV12 FW, you cannot play Youtube due to network issues. Please check it Thank you!! YK.Jung |
|
|
Hi YK, For "network issue", it is due to DNS which is modified by SPTEK on 10/7. You can set DNS manually by "setprop net.dns1 xxx.xxx.xxx.xxx"、"setprop net.dns2 xxx.xxx.xxx.xxx". (We use 8.8.8.8 / 8.8.4.4 for dns1 / dns2 here) I am not sure why "net.dns" is empty. Please help to check it with SPTEK. Thank you ! |
|
|
Hi YK, There is another build issue need to discuss with SPTEK. While I build without OTA files, there are compile errors. Please discuss with SPTEK if these files should be changed. Thank you ! device/amlogic/common ======================================================= diff --git a/sepolicy/file.te b/sepolicy/file.te index 1fd09cd..4533e4d 100644 --- a/sepolicy/file.te +++ b/sepolicy/file.te @@ -107,7 +107,7 @@ type aml_dsm_device, fs_type,sysfs_type; type irdeto_data_file, data_file_type, file_type; #btv_home_file -type btv_home_file, file_type, mlstrustedobject; +type btv_home_file, file_type, data_file_type, core_data_file_type, mlstrustedobject; #VaS type sysfs_eth_phy, fs_type, sysfs_type; ====================================================================== frameworks/base/ ===================================================================== diff --git a/core/api/test-current.txt b/core/api/test-current.txt index 3c95afa..a6f9f96 100644 --- a/core/api/test-current.txt +++ b/core/api/test-current.txt @@ -2743,7 +2743,7 @@ package android.view { method public static String actionToString(int); method public final void setDisplayId(int); field public static final int FLAG_IS_ACCESSIBILITY_EVENT = 2048; // 0x800 - field public static final int LAST_KEYCODE = 288; // 0x120 + field public static final int LAST_KEYCODE = 454; // 0x1c6 } public final class KeyboardShortcutGroup implements android.os.Parcelable { ==================================================================== |
|
|
Hi Kerwin OK , I will send it to SPTEK. and an compile error is occurring when SPTEK tries to use vendor/foxconn library. Please check the attached log file [ check_elf.zip ] Thank you !! YK.Jung |
|
|
Hi YK, Per updates on 10/17, BTF HAL libraries need to modified for ATV12. It is still under checking now. Thank you ! =============================== xxxx 4. Porting BTF HAL APIs * porting BTF HAL APIs on ATV12, there are some compile errors on ATV12. |
|
|
HI Kerwin SKB wants to know when the BTF HAL of the FXN model will be implemented (Currently, only FXN ATV12 cannot see the homeUI / Live AV. first of all, AV and Home menu must be operated. ) If the baisc function is completed within 1~2 days, there will be no problem, but if it takes more than that, SKB is requesting a schedule for each function. Currently, SPTEK is not able to verify the FXN model. Please let me know the implementation schedule for BTF HAL. Thank you YK.Jung |
|
|
Hi Kerwin 2) Free space ( https://jira.skbroadband.com/browse/FSTB12-3 ) remove unnecessary apps or libraries to free space on ATV 12 the apps below are not needed for smart3 , ( I checked with amlogic ) Please remove these =================================== OTAUpgrade2 ExoPlayer DroidLiveTv DroidLogicLiveTv dtvkitserver DroidTvSetting inputsource DvbAudioService ============================================ and please proceed quickly with the work that doesn't take long. When FXN checks, please remove useless apps and libraries And about GoogleTTS.apk -rw-rw-r-- 1 april4th april4th 46229368 9월 29 10:02 GoogleTTS.apk --> ATV12 -rw-rw-r-- 1 april4th april4th 30105941 9월 1 18:20 GoogleTTS.apk --> ATV10 15M increased on ATV12. can we use ATV10's for this? Please review it. Thank you!! YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. Add Auto-Upgrade feature => Done 2. Porting BTF HAL APIs * porting BTF HAL APIs on ATV12, there are some compile errors on ATV12. ==> compile errors is fixed, verifying BTF APIs. We will put libraries this week. (For SPTEK development first, some APIs may not work well) 3. Review commit list and do ATV12 porting ==> in progress, number of commit list is reduced from 892 to 786 4. remove unnecessary apps or libraries to free space on ATV 12 ==> plan to finish today Thank you ! |
|
|
Hi Kerwin SPTEK commited the necessary contents to FXN bitbucket now. compile error will be observed after repo sync but there will be no problem if you implement the BTF APIs and make free space. And if ATV12 do not currently have free space, first of all, To build, delete zemkids app and use GoogleTTS.apk as ATV10. Please check using GoogleTTS.apk(ATV10) at ATV12. Thank you!! YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. Porting BTF HAL APIs ==> Done * porting BTF HAL APIs on ATV12, there are some compile errors on ATV12. ==> Libraries are put to BitBucket on 10/21 2. Add DHCP option 60 and 225 ==> Done 3. Review commit list and do ATV12 porting ==> in progress, number of commit list is reduced from 786 to 696 4. remove unnecessary apps or libraries to free space on ATV 12 ==> packages below are removed, still check if we can remove more packages to fix compile error. =================================== OTAUpgrade2 ExoPlayer DroidLiveTv DroidLogicLiveTv dtvkitserver DroidTvSetting inputsource DvbAudioService ============================================ Thank you ! |
|
|
Hi Kerwin and jim Currently, SKB are considering adjusting the memory partition for the lack issue of free space. specially now, SKB is checking if it is possible to delete rsv partition. Amlogic FAE says he doesn't know about rsv partition And SWAN does not have a rsv partition. Please check the purpose(use) of rsv partition and whether it can be deleted. I wrote the wrong file name and uploaded it. ATV10_rsv_partition.PNG ==> ATV12_rsv_partition.PNG Thank you YK.Jung ATV10_rsv_partition.PNG (67,026 bytes) |
|
|
Hi Kerwin SPTEK has reported an issue to FXN. When calling the getDeviceForStream function, "speaker" was returned , not "HDMI" ( getDeviceForStream_issue.PNG ) Please check this issue Thank you YK.Jung getDeviceForStream_issue.PNG (22,702 bytes) |
|
|
HI Kerwin / jim https://jira.skbroadband.com/browse/AMANDROIDS-4 To solve issue that lack free space, please exclude the following files from FW build ================================================ 2.0M vendor/bin/oemcrypto_test_aml 28K vendor/bin/tee_stest 12K vendor/bin/test-systemcontrol 24K vendor/bin/secmem_test ================================================ This has been confirmed by Amlogic. Thank you!! |
|
|
Hi YK, Update current status for ATV12 porting 1. Verify BTF HAL APIs ==> in progress, solve sepolicy errors and check API behavior 2. remove unnecessary apps or libraries to fix compile error ==> Done. Remove unused package, WiFi kernel driver and files 3. Support edid.xml file in btv_home ==> plan to finish this week 4. Review commit list and do ATV12 porting ==> in progress, number of commit list is reduced from 696 to 676 B.R. Kerwin |
|
|
Hi Kerwin When I checked with the current bitbucket code , there is about 6.5M free space after build However, the menu image files were still not included. so we need more free space. Please change the "GoogleTTS.apk(46229368) file" in ATV12 to "GoogleTTS.apk(30105941) file" in ATV10 and commit it. In the case of INTEK, it has already been changed and Google test is in progress. Thank you!! |
|
|
HI Kerwin FXN deleted the odm_ext partition. It doesn't seem to have been completely deleted. An error is occurring in the "adb remount" command. Please check it Thank you!! YK.Jung odm_ext.PNG (14,887 bytes) |
|
|
Hi Kerwin In this mantis, it is difficult to check each detailed issue list. So I wrote down the request for each detail on the Google sheet below. https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 I think it would be better to proceed with the details on the Google sheet. And why don't we manage the overall status and important issues here? Please let me know if you have any other opinions. Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. Verify BTF HAL APIs ==> resolution changes are OK, will check for HDR/audio pass-through mode 2. Support edid.xml file in btv_home ==> Done 3. Verify and change eFAT/NTFS to read only ==> Done, both on ATV10 and ATV12 4. adb remount error in 'odm_ext' ==> Done 5. Review commit list and do ATV12 porting ==> in progress, number of commit list is reduced from 676 to 618 B.R. Kerwin |
|
|
Hi Kerwin SKB wants to know when the ongoing item will be finished. When can FXN finish the two items below? 1. Verify BTF HAL APIs 5. Review commit list and do ATV12 porting Please give me a rough schedule And are there any important items left that are not on the schedule? FYI, INTEK is doing a Google test and listing the fail items. Thank you YK.Jung |
|
|
Hi Mr. Jung, Update current status for ATV12 porting 1. Verify BTF HAL APIs ==> resolution changes are OK, will check for HDR/audio pass-through mode (11/4) 5. Review commit list and do ATV12 porting ==> in progress, number of commit list is reduced from 676 to 568 (11/25) |
|
|
Hi YK, Update current status for ATV12 porting 1. Verify BTF HAL APIs => Done However, audio pass-through doesn't work on current ATV12 BSP. The audio profiles are not updated correctly by AML audio HW library. Please help to check it with AML Korea FAE. 2. Porting modifications in BT stack => Done Need SPTEK's pairing App to do more tests. 3. NUGU voice recognition => pending NUGU app generate tombstone while app starts. 4. Review commit list and do ATV12 porting ==> in progress, due to 11/25 B.R. Kerwin |
|
|
HI Kerwin 1. about "audio pass-through" In order to discuss with AML Korea FAE, I have to understand the issue. If you explain the issue part on the log, I will discuss it with AML Korea FAE. Please explain the log and the issue in detail. Thank you YK.Jung |
|
|
Hi YK, On ATV12, user can check audio formats in Google Settings. (Google Setting -> Device Preferences -> Display & Sound -> Advanced sound settings) Supported audio formats should be listed in "ENABLED FORMATS" if sink (TV or AVR) devices support. Now, we don't see supported audio format listed in the page when we set audio output to "external device" in SKB UI. It works well on other devices with ATV12. (You can see attached picture) Please discuss it with AML Korea FAE. Thank you. Kerwin surround_sound_enabled_format.png (153,314 bytes) |
|
|
Hi YK, Update current status for ATV12 porting 1. Porting NUGU voice recognition and verify by Foxconn's AudioRecord app (11/14) 2. Verify HDCP and DRM keys by ExoPlayer ==> Done, firmware.le (HDCP) path is wrong. It is fixed and commit to BitBucket 3. Porting BT related modifications in BT stack and Bluetooth package (11/14) 4. Verify DDP library with online stream ==> Done 5. Debug HDMI audio passthrough issue (https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1533#c11170) B.R. Kerwin |
|
|
HI Kerwin I have a question about "audio pass-through" I think the issue will be resolved if you know the supported audio formats listed. Is it correct? If so, how did you get the corresponding formats list in the previous Android Q? FXN has already been implemented in ATV10, but I guess it doesn't work in ATV12. If you tell me the function(code level) used in ATV10, I will discuss it with AML and let you know the function in ATV12 that has the same function. Thank you YK.Jung |
|
|
Hi YK, There are changes in Frameworks and Google Settings on ATV12. So the items are different from ATV10. The above picture is got from ATV12 released by AML on Aug. for another platform. I know AML will put supported formats in sysfs node after parsing EDID. (/sys/class/amhdmitx/amhdmitx0/audio_cap) This part is correct on current ATV12 BSP for Smart3. Thank you ! |
|
|
Hi Kerwin I think I misunderstand your situation now I'm inquiring again. 1) about audio pass-through => Is this issue resolved now? If it hasn't been solved, please let me know what I can help you with 2) about "ENABLED FORMATS" at Google Settting menu at ATV12 => you said that "The audio profiles are not updated correctly by AML audio HW library." This content is correct that Amlogic should check, but is there any problem with implementation due to this symptom? Please let me know if there is any problem I think , it seems that "audio pass-through" has nothing to do with this symptom. Thank you!! |
|
|
Hi YK, 1) Issue is not fixed yet. But there is no problem on ATV12 released on Aug. So I think AML should have patch for this issue. 2) I think there may be a problem. Sink supported formats should be in "ENABLED FORMATS" if we set to passthrough mode, Thank you! |
|
|
Hi YK, Update current status for ATV12 porting 1. Porting NUGU voice recognition and verify by Foxconn's AudioRecord app (11/14) => debugging device selection in audio HAL/frameworks 2. Porting BT related modifications in BT stack and Bluetooth package ==> Done 3. Verify RTL8723du USB WiFi dongle on ATV12 for xTS => driver is ok but we can't see scan list on Settings UI, need to check it with AML 4. Review commit list and do ATV12 porting ==> in progress (426), due to 11/25 B.R. Kerwin |
|
|
Hi Kerwin About 3) Please tell me the product name(include photo) of the "RTL8723du USB WiFi dongle" FXN is using I would like to purchase the same thing here if it is possible. Thank you YK.Jung |
|
|
Hi YK, We buy the USB WiFi dongle from China 'Taobao'. The brand name is "GRIS", you can check attached picture for reference. Thank you ! Kerwin GRIS_USB_WiFi_Dongle.jpg (80,643 bytes) |
|
|
Hi YK, Update current status for ATV12 porting 1. Porting NUGU voice recognition and verify by Foxconn's AudioRecord app (11/18) => need to add permissions 2. Verify RTL8723du USB WiFi dongle on ATV12 for xTS => Done, current AML's implementation doesn't support hotplug. USB WiFi dongle must be inserted before device boots up. 3. Check 'GTVS_COMPRESSED_PREBUILTS' flag => set the flag in vendor/google_gtvs/products/gtvs.mk and there is nothing changed. We also search document on Partner Center and doesn't find useful information 4. Review commit list and do ATV12 porting ==> in progress (356), due to 11/25 B.R. Kerwin |
|
|
HI Kerwin SKT is planning to do an emergency recovery FTP test soon. When I did the OTA test, OTA is not available with the previous build date. at here , Emergency recovery FTP FW is always the previous build date. so , even though it was a previous build date, please implement it so that it can be updated. please check number 10 at below link https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 Thank you!! YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. Porting NUGU voice recognition and verify by Foxconn's AudioRecord app (Done) => We also use "nugu-stb-bfx_at100-user-3.14.1.apk" to test, But NUGU app replies "Service is not available" after we press NUGU button 2. HDMI audio passthrough issue (Done) => AML's library (droidlogic.software.core) was not included in current BitBucket source. So HDMI plugin event is not sent to audio HAL. 3. Update rtl8723du driver for xTS fail (Done) => update rtk driver to 5.13 4. Check downgrade for SKB emergency recovery FTP test ==> local test is ok, will double confirm commits on BitBucket B.R. Kerwin |
|
|
Hi Kerwin We are planning to test the stability with 6 STBs (SD FW) from this week. The problem now is that no-signal is displayed on TV after sleep and wakeup. There is no problem with Samsung/LG TV, but there is a problem with the test monitor and UMAX. Because of this, it is difficult to proceed with the stability test. Please fix the issue quickly. [number 3] at below link https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 Thank you!! YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. Debug issue "no-signal is displayed on TV after sleep and wakeup" => in progress, issue is reproduced on a LG monitor, due to 11/25 2. Verify HDMI audio passthrough issue on PlayMovies (Done) => pass, we see DDP format on AVR while playing video by PlayMovies 3. Check 'LOCAL_COMPRESSED_MODULE' flag on webview package => in progress, due to 11/24 4. Check downgrade for SKB emergency recovery FTP test (Done) ==> push to BitBucket B.R. Kerwin |
|
|
HI Kerwin We are planning to do a stability test on 6 STBs with ATV12 FW soon. Before that, there is an additional request from SPTEK and SKB. Secure FW is being upgraded on the ND board. then user must use the Amlogic burning tool because it does not boot after the upgrade. Please solve this issue. [number 11] at below link https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. Debug issue "no-signal is displayed on TV after sleep and wakeup" => Done, issue is gone after porting patch from ATV10 2. Check 'LOCAL_COMPRESSED_MODULE' flag on webview package => Done, commit to BitBucket 3. Review commit list and do ATV12 porting => Done, Fii's patches are pushed to BitBucket. 4. Add a checking to avoid SD OTA file upgrade on ND boards. => We've added a checking before doing OTA upgrade, still doing tests, due to 11/30 5. Merge AML 11/28 patches on common SDK => due to 11/29 BTW, for return value of 'getDeviceForStream', please check with SPTEK if issue still exists. It should be OK after we fix HDMI audio passthrough issue. [item 8] on GoogleDrive document https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 B.R. Kerwin |
|
|
Hi Kerwin Please apply passive standby function to ATV12. Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. Add a checking to avoid SD OTA file upgrade on ND boards. => Function implementation is done, will commit ot BitBucket today 2. Merge AML 11/28 patches on common SDK => Done 3. Check issue that RCU IR control doesn't work under 'user' build. => due to 12/5 4. Porting Security patch to 2022-11 => due to 12/1 5. Prepare document on Mantis#1568 => due to 12/9 B.R. Kerwin |
|
|
Hi Kerwin At the start of BT pairing at ATV12 FW the keycode value is observed to be 0. (if you press * + # at the same time) 12-02 15:37:36.727 3716 3834 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 0 And if you press "나가기" at RCU the keycode value is observed to be 0 12-02 15:41:55.055 3716 3834 D WindowManager: interceptSkbFuctionKeyBeforeDispatching keycode = 0 so It's not working properly. [number 7] at below link https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 Please check it Thank you YK.Jung |
|
|
Hi YK, Current keylayout file doesn't contain SKB special functions. We will update it later. Thank you ! |
|
|
Hi Kerwin The QA team is reviewing the ATV12 FW, but there are difficulties when testing. Please fix the keylayout by this morning. And there is a plan to release ATV12 Test FW in SKB at today Thank you!! YK.Jung |
|
|
Hi YK, IR keylayout is updated on BitBucket. Thank you ! |
|
|
Hi YK, Update current status for ATV12 porting 1. Check issue that RCU IR control doesn't work under 'user' build. => Done, commit to BitBucket this morning 2. Porting Security patch to 2022-11 => Done 3. Fix SKB function keys don't work under IR mode => Done, commit to BitBucket this morning 4. Prepare document on Mantis#1568 => BTF API is done, will start to run xTS to get report B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 porting 1. Fix can't run fastboot command for xTS test. => Done 2. Add a property to use Google DNS for xTS tests. => Done 3. Prepare document on Mantis#1568 => start to run xTS to get report B.R. Kerwin |
|
|
Hi Kerwin And please apply passive standby function to ATV12. Please let me know when this work will start and when it will be completed (Expected schedule) Thank you YK.Jung |
|
|
HI Kerwin The emergency recovery FTP test continues to fail. When I tested it with the SD version, it was not updated to the previous build date. (951 -> 950) If you update as below, a failure occurs. from http://altserver02.duckdns.org/release_by_fxn/smart3/k000c-534r951_SD-20221208-BFX-AT100/ to http://altserver02.duckdns.org/release_by_fxn/smart3/k000c-534r950_SD-20221128-BFX-AT100/ Please check it Thank you YK.Jung |
|
|
Hi YK, It seems to be blocked by patch which avoid SD FW upgrade on ND board. The patch is committed on 11/30. FW release earlier than 11/30 will have such issue. BTW, we also commit 2022-11 security patch on 11/29. It will have problem if you downgrade to older version. Please use another FW to do downgrade test. Thank you ! |
|
|
Hi Kerwin (reminder) about passive standby function at ATV12 Please let me know the progress or expected schedule of the work at ATV12 Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1. Fix ATV10 to ATV12 OTA fail => Done. It is doing 2-steps upgrade after merging AML's patch 2. Add missing environment to avoid SD FW updated on ND board => Done 3. Update GMS core and packages for xTS test => updated on local, start to run VTS this morning 4. Check system fails to boot after flashing GSI. => in progress For passive standby mode support, the plan is 12/15 ~ 12/29. B.R. Kerwin |
|
|
Hi Kerwin After connecting RCU to STB with BT, using RCU for 1~2 hours causes issue of RCU not working When using the same RCU, the issue is only occurring in ATV12. Please check the issue. Issue #25 https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 And please update the progress . Thank you!! YK.Jung |
|
|
Hi YK, For RCU BT issue, please provide log and reproduce steps. Update current status for ATV12 porting 1. Update GMS core and packages for xTS test => Done, there is a fail in VTS, checking root cause 2. Check system fails to boot after flashing GSI. => Done 3. For current xTS status, please check it here https://docs.google.com/spreadsheets/d/1OKc7HVUg9ppu6Ie5-svmI-5yQC3w0sZJOq2DBbI_PWg/edit#gid=791333398 4. passive standby mode support, the plan is 12/15 ~ 12/29. B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 porting 1. passive standby mode support => finish patch porting from ATV10, will do more tests 2. merge AML patches-1214 from common SDK => Done 3. For current xTS status, please check it here CTS: in progress GTS: 2 fails STS: done VTS: done GSI: in progress TVTS: 32 fails CTS-V: 3 fails Smoke Test: in progress YouTube Test: done BTS: done https://docs.google.com/spreadsheets/d/1OKc7HVUg9ppu6Ie5-svmI-5yQC3w0sZJOq2DBbI_PWg/edit#gid=791333398 BTW, there are xTS fails which need your help to check with other parties. 0001555, 0001576, 0001577, 0001578 Thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 porting 1. xTS self-test CTS: 105 fails(under analysis, wifi realted issues are the most), 5 modules are still in progress GTS: 2 fails -> 1 fail (0001578) GSI: 194 fails(under analysis, wifi realted issues are the most), 3 modules are still in progress TVTS: 32 fails(HDMI related) CTS-V: 3 fails(0001576, 0001577, 1 fail is still under analysis) Smoke Test: in progress Thank you ! B.R. Kerwin |
|
|
Hi Kerwin Please review the issues below. 1) bt pairing issue ( high priority ) # 25 https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 2) review free space ( normal priority ) There is currently no free space ( free space 8.5M ) Please review the "free space" in excel and apply it if there is any part that can additional free space. # issue Topic == "free space" https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 3) passive standby ( normal priority ) When the "passive standby" test is completed, please send the test image to me I have to report the test results to SKB next week. 4) etc (low ) # 23 , # 24 , https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 Thank you!! YK.Jung |
|
|
Hi YK, 1) bt pairing issue ( high priority ) ==> per update in https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1533#c11478, please check if it is reproducible and provide logs. 2) review free space ( normal priority ) ==> remove remotecfg, bootvideo, bootvideo.zip and default_wallpapaer.png For libdvr, libsecdmx_release, dsp_util, hifidsp folders, Smart3 doesn't include these packages. 3) passive standby ( normal priority ) ==> 15.534.r204 includes passive standby, you can use it to test 4) #23 mount point of USB storage ==> under analysis |
|
|
Hi YK, Update current status for ATV12 porting 1. xTS self-test ==>try to solve system enter passive standby while doing WiFi related tests. If we change USB port as device mode and plug USB calbe to PC, system won't go to passive standby mode. 2. Remove unused files for Smart3 bootvideo 1773398 bytes bootvideo.zip 671474 bytes default_wallpaper.png 300796 bytes remote.cfg 598 bytes 3. Study LOCAL_COMPRESSED_MODULE with stub APK ==> Need to implement a stub APK with same signature to decompress .gz APK. This also means GTVs can't use LOCAL_COMPRESSED_MODULE because we don't have GTVs keys. We can only apply it for APK with platform key, such as Camera, Live. 3rd party APKs need other companies's help to provide stub APK. 4. #23 mount point of USB storage ==> under tests, due to 12/28 Thank you ! B.R. Kerwin |
|
|
Hi Kerwin Please check below issues # 27 (Remove delay at HDMI_Set_Enable) , #17 (hdmi-edid.xml) https://docs.google.com/spreadsheets/d/1rheB38TCjl0_aYok0E8FfTFg1PlWOMt22CH2PKzrUD4/edit#gid=188263279 and please check ( # 23 , # 24 ) Thank you! YK.Jung |
|
|
Hi Kerwin SKB distributed some ND/SD FW to developers, but STB not booting issue observed When we checked, it wasn't working as I expected please check attached file ( ATV12_10_secure_nonSecure_test_result.PNG ) That is, there is a problem with the Secure Board <-> Non-Secure Board / ATV10 <-> ATV12 update now. Please fix this issue first (high priority) Thank you YK.Jung ATV12_10_secure_nonSecure_test_result.PNG (27,507 bytes) |
|
|
Hi YK, Update current status for ATV12 porting 1. xTS self-test ==> still try to solve system enter passive standby while doing WiFi related tests. If we change USB port as device mode and plug USB calbe to PC, system won't go to passive standby mode. 2. #23-mount point of USB storage, #27-Remove delay at HDMI_Set_Enable ==> commit to BitBucket, done 3. #24-FW release naming rule ==> commit to BitBucket, done 4. #28-NUGU is not working ==> It is blocked by AudioPolicyService on ATV12. If we change it in Framework, NUGU works well. Still checking for root cause 5. Secure Board <-> Non-Secure Board / ATV10 <-> ATV12 update fails ==> Per discussed, ATV12 -> ATV10 is not under consideration. (https://172.18.223.170/vaas/view.php?id=1533#c11047) We will add a check to prevent ATV12->ATV10 update. And non-secured boards are for SW development only. We think the test cases are not important. Please help to discuss it with SKB. Thank you ! B.R. Kerwin |
|
|
Hi Kerwin About #5 Secure Board <-> Non-Secure Board / ATV10 <-> ATV12 update fails SKB tells me to consider non-secure boards. (INNOPIA has already considered non-secure boards and INTEK is working on it.) Additionally, it should be downgraded to ATV12 -> ATV10. (SKB changed the guide , INNPIOA has already applied the downgrade method.) I marked the changed items in red. Please check it Thank you YK.Jung ATV12_ATV10_update_expected.PNG (27,934 bytes) |
|
|
Hi YK, Update current status for ATV12 porting 1. xTS self-test ==> still try to solve WiFi related tests. adb will be disconnected and the following cases can't be tested 2. #28-NUGU is not working ==> fixed and commit to BitBucket 3. Secure Board <-> Non-Secure Board / ATV10 <-> ATV12 update fails ==> working on Secure Board <-> Non-Secure Board first. Still checking on AML's defend key Thank you ! B.R. Kerwin |
|
|
Hi Kerwin The meeting about ATV12 update has been changed to every day(Mon ~ Fri) since this year. I wrote down the time for the daily meeting. (Korea Meeting Time ) Mon : 16:00 ~ 17:00 Tue : 15:00 ~ 16:00 Wed : 17:00 ~ 18:00 Thu : 15:00 ~ 16:00 Fri : 11:00 ~ 12:00 Please update the progress by 2 hours before the meeting. Thank you YK.Jung |
|
|
Hi Kerwin 1) review free space ( high priority ) An error is occurring when building ND FW today. when I removed zemkids app and app_plus app , FW was created. Please review the free space additionally 2) CEC function is not working at ATV12 3) please check build script The upgrade file is being created in the out folder, not in the Release folder. out/target/product/BFX-AT100/usb_bfx-at100_V15.534.207.zip Please make it the same as ATV10. Thank you YK.Jung |
|
|
Hi Kerwin SKB plans to build FW for ATV12 every Tuesday and Thursday. That is , there will be an FW build today ( please check FW build issue [free space] ) and please update the progress until 13:00 Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1) review free space ( high priority ) => 1. remove Camera app (about 4MB) 2. remove Live TV app temporarily, will add it back and change it to a compressed apk 2) CEC function is not working at ATV12 => checking 3) please check build script => Now, it is the same as ATV10. We copy OTA file to 'Release' folder in another script for formal release Thank you ! B.R. Kerwin |
|
|
Hi YK, i update OTA upgrade status and we are still checking for failure cases. Jerry |
|
|
Hi kerwin The following is SKB's request. 1) When can FXN finish all the issues that occurred during ATV12 Google test ? Please let me know the schedule. 2) A new app will be added to ATV12. it is necessary to more than 40M free space. 3) Please tell me about the remaining tasks that FXN has to do in ATV12. 4) There is Lunar New Year's Day this month. please let me know about the holidays of FXN and 3PL. Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 porting 1) review free space => Per update, we can't apply LOCAL_COMPRESSED_MODULE on GTVs packages due to signature. Even we apply LOCAL_COMPRESSED_MODULE on LiveTV, only more 12 MB is available. Currently, we think it is better to apply LOCAL_COMPRESSED_MODULE on 3rd applications, such as ZemKids. 2) CEC function is not working at ATV12 => Fixed and commit to BitBucket 3) Add secure to non-secure protection for OTA updates => commit to BitBucket Thank you ! B.R. Kerwin |
|
|
Hi Jerry 3) Add secure to non-secure protection for OTA updates => commit to BitBucket Please send me ND/SD fw if it's solved. then we'll check again here. Thank you YK.Jung |
|
|
Hi YK, i upload ND/SD test F/W to ALT server. Please download and verify. FW link: /release_by_fxn/temp_wfh/jerry/eagle Jerry |
|
|
Hi Kerwin reminder , https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1533#c11637 ============================================================================ The following is SKB's request. 1) When can FXN finish all the issues that occurred during ATV12 Google test ? Please let me know the schedule. 3) Please tell me about the remaining tasks that FXN has to do in ATV12. 4) There is Lunar New Year's Day this month. please let me know about the holidays of FXN and 3PL. ========================================================================================= Thank you YK.Jung |
|
|
Hi Jerry we checked the fw ( /release_by_fxn/temp_wfh/jerry/eagle ) , it's ok Please apply it to main branch ( ATV10 / ATV12 ) Thank you YK.Jung |
|
|
Update current status for ATV12 porting 1) review free space => looking Stub APKs on GTVs branch to get more free storage space 2) Verify patch to solve TVTS 'testAudioSamplingRatesMatch' test cases => commit to BitBucket. Now, TVTS could be clean. For other questions When can FXN finish all the issues that occurred during ATV12 Google test ? => Current, we are working on issue for CTS Wifi related tests. During testing, network will be down and adb will also disconnected. So we are trying to solve it with AML's help. Please tell me about the remaining tasks that FXN has to do in ATV12. => ATT Daemon is not applied. We plan to add it after xTS is clean. There is Lunar New Year's Day this month. please let me know about the holidays of FXN and 3PL. => FXN: 1/20 ~ 1/29, 3PL should be the same, but need to double check B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) review free space => Add Stub apks for WebView and Trichromelibrary. From system log, Webview and Trichromelibrary are decompressed and installed successfully. (logcat -s PackageManager) 2) Add Live TV => It was removed due to storage shortage. Now we use compressed Webview so add 'LiveTV' back. 3) xTS self-test There are some xTS related issues on Mantis, please help to check with SPTEK to solve it. (Category: 'xTS certification') CTS: 1. Listening port issue https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1592 2. CtsScopedStorageDeviceOnlyTest can not be finished: https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1585 3. CtsHostsideWebViewTests: Maybe related SKB change webview provider (in progress) 4. CtsHdmiCecHostTestCases: 9 fails (in progress) 5. CtsNetTestCases & CtsWifiTestCases we have ethernet adb disconnect issue, can not finished the module (in progress) GTSWebview provider https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1578 GSI 3 fail 1. Listening port issue https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1592 2. CtsAppTestCases android.app.cts.ActivityManagerFgsBgStartTest#testFgsLocationStartFromBG (in progress) 3. CtsWifiTestCases android.net.wifi.cts.WifiManagerTest#testSave (in progress) TVTS *TvtsHdmiHostTestCases Module can not be executed correctly. (if we revert Amogic side effect patch, we can pass it) https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1582 CTSVerifier 3 fail 1. Screen off intent: https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1577 , https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1586 2. Resolution issue: https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1582 3. IME issue: https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1576 SmokeTest: 1. Lose foucs after standby/resume https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1586 2. Notification issue of USB insert B.R. Kerwin |
|
|
Hi Kerwin The audio music volume only is not adjustable on ATV12. There is no problem with other manufacturers, and only FXN model is observing this issue. SPTEK's analysis shows that the gain value of AUDIO_STREAM_MUSIC (3) is not normal. Please check it Thank you YK.Jung |
|
|
Hi Kerwin Currently, SPTEK has committed to force the audio volume control to operate. this code is a temporary code and will be revert later. Please check why FXN STB only can't get gain from AUDIO_STREAM_MUSIC. Thank you YK.Jung SPTEK_temp_commit.PNG (53,113 bytes) |
|
|
Hi YK, We have an internally discuss about ATV12 downgrade to ATV10. We will modify the update method to a one-time update and execute google factory reset after the OTA downgrade is completed. This will ensure that the OTA downgrade can be done without problems. Jerry |
|
|
Hi Jerry It is not a problem that Google factory reset must be performed after downgrading from ATV12 to ATV10. Downgrading from ATV12 to ATV10 will not be for end-user(customer). Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check 'volume adjust on AUDIO_STREAM_MUSIC' reported from SPTEK. ==> in progress 2) Support ATV12 to ATV10 downgrade ==> Must have a factory reset after system downgrade from ATV12 to ATV10. Need ALT's help to discuss with SKB. 3) xTS self-test: a. we have a solution to avoid adb disconnected during CtsNetTestCases & CtsWifiTestCases b. ckeck how to fix 'CtsScopedStorageDeviceOnlyTest' with SPTEK. B.R. Kerwin |
|
|
Hi Kerwin - How long can all Google issues be resolved? Please let me know the actual schedule by tomorrow. and if there is any blocking issue, please let me know. - please let me know about the holidays of 3PL. and please update the progress of the issue within 30minutes Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check 'volume adjust on AUDIO_STREAM_MUSIC' reported from SPTEK. ==> in progress 2) Support ATV12 to ATV10 downgrade ==> will commit to BitBucket after verification is done 3) xTS self-tests: a. verify side-effect of solution to avoid adb disconnected during CtsNetTestCases & CtsWifiTestCases b. check CEC test fails in CTS - please let me know about the holidays of 3PL ==> 3PL has a day off on 1/16. For Lunar New Year's Day, the duration is 1/20 ~ 1/29 B.R. Kerwin |
|
|
Hi YK, We got the information from 3PL that if the submission is provided after Jan. 14th, they can't guarantee that the test and submission can be completed before Jan. 31th. Thanks, Jacky |
|
|
Update current status for ATV12 OS development 1) Check 'volume adjust on AUDIO_STREAM_MUSIC' reported from SPTEK. ==> in progress 2) Integrate ATTDaemon to ATV12 ==> have problem to add ATTDaemon APK due to storage shortage. 3) xTS self-tests: a. verify side-effect of solution to avoid adb disconnected during CtsNetTestCases & CtsWifiTestCases b. check CEC test fails in CTS c. 'CtsHostsideWebViewTests' is passed by using latest WebView APK and Standard Luncher. It may need Digicap's review. BTW, ATV10 self-test is also in progress by QA. Some items of ATV12 need QA to verify will be postpone. Please help to explain to SKB. Thank you! B.R. Kerwin |
|
|
Update current status for ATV12 OS development 1) Check 'volume adjust on AUDIO_STREAM_MUSIC' reported from SPTEK. ==> in progress, it seems Framework doesn't know how to deal "AUDIO_STREAM_BTV". still checking if there is missing patch from SPTEK 2) xTS self-tests: a. work with QA to verify CtsNetTestCases & CtsWifiTestCases b. check CEC test fails in CTS 3) checking log in Mantis 0001601 B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check 'volume adjust on AUDIO_STREAM_MUSIC' reported from SPTEK. ==> in progress, volume stream index is different from ATV10. doing review for the changes 2) xTS self-tests: a. Network and WiFi tests seems clean. will release a FW to QA to double check all CTS test cases during this weekend. b. check CEC 7 fails in CTS B.R. Kerwin |
|
|
Hi Kerwin SKB made this jira. https://jira.skbroadband.com/browse/FSTB12-38 That is , please apply the patch below to ATV12 and verify it. https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1490 Thank you YK.Jung |
|
|
Hi YK, About the issue "can't get gain from AUDIO_STREAM_MUSIC." 1. The gain value is got from AUDIO_STREAM_BTV. 2. Please check the attached patch (under frameworks/base). The value NUM_STREAM_TYPES should be 15. 3. Before applying the patch, gain value is nan for index 24. After applying the patch, gain value is -16.035351 for index 24. This modification is located in SPTEK's commit. It's better to let SPTEK apply this patch. audio_btv.patch (590 bytes) |
|
|
Hi Bcan I reported it to SPTEK https://jira.skbroadband.com/browse/FSTB12-39 Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check 'volume adjust on AUDIO_STREAM_MUSIC' reported from SPTEK. ==> Done, clarify issue and SPTEK already fix and commit to BitBucket 2) Porting ATTDaemon ==> Done, get more free space and add ATTDaemon as a prebuilt APK 3) xTS self-tests: a. Network and WiFi tests seems clean. FW is built on 1/13. double check for all CTS test cases is still in progress. b. check and clarify CEC related fails in CTS B.R. Kerwin |
|
|
Hi Kerwin (reminder) 1) https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1607 2) https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1533#c11762 please apply the patch below to ATV12 and verify it. https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1490 Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Verify functions of ATTDaemon on ATV12 ==> in progress 2) Manti#1607 for LED issue ==> in progress, sepolicy related issue 3) Porting Mantis#1490 to ATV12 ==> in progress, behavior is different from ATV10, still check on it 4) xTS self-tests: a. Network and WiFi tests seems clean. FW is built on 1/13. double check for all xTS test cases is still in progress. b. check and clarify CEC related fails in CTS B.R. Kerwin |
|
|
Hi Kerwin Please let me know the overall fail situation that occurred during the Google test and the schedule to solve the issues. I need to know the overall situation so that I can discuss whether the SKB schedule is OK or not. Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development xTS result will be updated later today 1) Verify functions of ATTDaemon on ATV12 ==> in progress, due to 1/19 2) Manti#1607 for LED issue ==> Done 3) Porting Mantis#1490 to ATV12 ==> Done, commit to BitBucket 4) Mantis#1612: missing YouTubeKids app ==> There is not enough storage to add YouTubeKids as a prebuit APP.(16MB) Even if we apply LOCAL_COMPRESSED_MODULE on ZemKids app, it is still failed to build FW. 5) Try to apply LOCAL_COMPRESSED_MODULE on ZemKids app ==> Done. B.R. Kerwin |
|
|
Hi YK, Please check xTS result on link below (0119) https://docs.google.com/spreadsheets/d/1OKc7HVUg9ppu6Ie5-svmI-5yQC3w0sZJOq2DBbI_PWg/edit#gid=2051529080 Thank you ! |
|
|
Hi Kerwin https://docs.google.com/spreadsheets/d/1OKc7HVUg9ppu6Ie5-svmI-5yQC3w0sZJOq2DBbI_PWg/edit#gid=2051529080 ==> I added a comment to the document. Please check the following issues quickly https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1620 [Smart3/UHD4] Change Boot Still Image (ATV10 UI536 / ATV12 UI537) https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1605 [Smart3][ATV12] Audio volume level (0~32) measurement request https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1621 [Smart3][ATV12] HDR menu Issue (Permission denied) https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1618 [Smart3][ATV12] SELinux : avc: denied ( vendor.amlogic.hardware.hdmicec::IDroidHdmiCEC ) https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1619 [Smart3][ATV12] Kids RCU(KR01) issue https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1610 [Smart3][ATV12] MIC does not work in karaoke app https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1616 [Smart3][ATV12] Unable to enter removable storage information when inserting USB Stick in NTFS format https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1613 [Smart3][ATV12] Free space shown as 0B when inserting USB Stick(FAT32) https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1569 [Smart3][ATV10][VoC] RCU OK button not working https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1612 [Smart3][ATV12] YouTube Kids App does not displayed https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1615 [Smart3][ATV12] Audio sound choppy issue after JBL BT speaker connection https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1611 [Smart3][ATV12] Issues after connecting USB mouse (low priority) Thank you!! YK.Jung |
|
|
Hi Mr. YK and Kim, Update current status for ATV12 OS development xTS result is updated on 1/19, no updates on today due to long holiday 1) Verify functions of ATTDaemon on ATV12 ==> there are few functions still under verification, due to 2/1 2) Mantis#1612: missing YouTubeKids app ==> There is not enough storage to add YouTubeKids as a prebuit APP.(16MB) Even if we apply LOCAL_COMPRESSED_MODULE on ZemKids app, it is still failed to build FW. Need to try to compress SKB Home UI APK. 3) Try to apply LOCAL_COMPRESSED_MODULE on SKB Home UI APK ==> in progress. B.R. Kerwin |
|
|
Hi Mr. Kim, Update current status for ATV12 OS development 1) Mantis#1612: missing YouTubeKids app ==> Done by using compressing flag for ZemKids and Home UI APKs 2) Try to apply LOCAL_COMPRESSED_MODULE on SKB Home UI APK ==> Done 3) Solve selinux issue for Mantis 0001618(CEC), 0001621(HDR) => Done 4) Check Mantis issue 0001619 for notification of Kids RCU charging => in progress, some parts need SPTEK to check 5) Porting patch for Mantis 0001582 (side effect of HWC_ENABLE_REAL_MODE) => in progress 6) Check Mantis issue 0001610 for Karaoke Mic => in progress BTW, please check Mantis issues with "xTS certification" tag which are reported by us. These are important to get Google approval for Eagle ATV12 and should be solve by SPTEK/Digicap. B.R. Kerwin |
|
|
Hi Mr. Kim, Update current status for ATV12 OS development 1) Check Mantis issue 0001619 for notification of Kids RCU charging => missing keys are commited to BitBucket 2) Check Mantis 0001610-MIC does not work in karaoke app => We can't reproduce issue. Check for log provided by ALT. 3) Check Mantis 0001626-Press volume key cause SetupWizard to crash => integrate GTVs and build a FW based on pure AML ADK. The issue doesn't happen. So we think root cause maybe SPTEK's modification in Frameworks. 4) xTS certification: Verify Mantis 0001578 0001591 0001630 issues B.R. Kerwin |
|
|
Hi Mr. Kim, Update current status for ATV12 OS development 1) Check Mantis 0001610-MIC does not work in karaoke app => in progress, check for log provided by ALT. 2) Check Mantis 0001626-Press volume key cause SetupWizard to crash => check selinux rules 3) Mantis#1620-Change Boot Still Image => Done 4) xTS certification: Verify Mantis 0001627 0001630 0001631 issues B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 0001610-MIC does not work in karaoke app => in progress, check reproduce steps and log files 2) Check Mantis 0001626-Press volume key cause SetupWizard to crash => Done, commit to BitBucket 3) xTS certification => * Check issue it is not easy to pair with BT gamepad for Smoke Test * Verify CEC related issues and updates on Mantis 0001608 Based on our plan, we will do a final xTS self-test from this week. Please check Mantis issues with "xTS certification" tag which are reported by us ASAP. These are important to get Google approval for Eagle ATV12. Thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 0001610-MIC does not work in karaoke app => in progress 2) Revert compression of HomeUI and check HomeUI crash issue => Done, commit to BitBucket 3) xTS certification => * Check issue it is not easy to pair with BT gamepad for Smoke Test Based on our plan, we will do a final xTS self-test from this week. Please check Mantis issues with "xTS certification" tag which are reported by us ASAP. These are important to get Google approval for Eagle ATV12. Thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 0001610-MIC does not work in karaoke app => in progress, please provide another log on Mantis 2) Mantis#1644: apply patches in AML auto-patch folder 3) xTS certification => * Check issue it is not easy to pair with BT gamepad for Smoke Test => Done * Work with SPTEK to implement 'skip DNS' for xTS verification => Done * Verify SPTEK related issues for xTS Based on our plan, we will do a final xTS self-test from this week. Please check Mantis issues with "xTS certification" tag which are reported by us ASAP. These are important to get Google approval for Eagle ATV12. Thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 0001610-MIC does not work in karaoke app => in progress, check pull pointer while creating audio patch 2) Mantis#1612: Add YouTubeKids as a built-in APP => Done 3) xTS certification => * Verify SPTEK related issues for xTS (Mantis 0001608, 0001624) Based on our plan, we will do a final xTS self-test from this week. However, we don't start self-test yet because 'audio mute after booting up' and 'IME can't be used' issues. And there are some issues with 'xTS certification' category on Mantis. Please help to check, thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 0001610-MIC does not work in karaoke app => in progress, please ask AML Korea to check null pointer in audio HAL 2) Mantis#1589: porting commit from ATV10 => Done 3) Check passive standby issues on ATV12 => in progress 4) xTS certification => * Do xTS self-test on 15.537.8 release There is a black screen issue about Home UI, Jason has reported last week. Please help to check, thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 0001610-MIC does not work in karaoke app => pending, wait for AML Korea;s response 2) Check passive standby issues on ATV12 => in progress, check BT RCU disconnected issue 3) Check Mantis 0001611 - Issues after connecting USB mouse => in progress, check 'back' key for mouse right-click 4) xTS certification => * Solve a STS failed item with latest STS tool => Done * Do xTS self-test on 15.537.8 release => in progress Based on our plan, we already start to do final xTS self-test. There is a black screen issue about Home UI, Jason has reported last week. And there are some issues with 'xTS certification' category on Mantis. Please help to check, thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 0001610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check passive standby issues on ATV12 => in progress, check BT RCU disconnected issue 3) Check Mantis 0001611 - Issues after connecting USB mouse => in progress, porting patch and verify 4) Check Mantis 0001653 - selinux rules for "vendor.skb.hdmi.*" => Done 5) xTS certification => * xTS self-test on 15.537.8 CTS/CTS-ON-GSI: in progress, there are many media failures, it will cause many timeouts CTS-Verifier: not started VTS/TVTS/STS/GTS/YouTubeTest: done SmokeTest: In Progress, Current new issue: *RCU BA01 QuickSet not work (after pairing, change input source/tv volume not works) *Can not go to suspend resume 0001651 *RCU can't control by DPAD in the "Game&App" page of launcher UI 0001652 Please help to check, thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check passive standby issues on ATV12 => in progress, check BT RCU disconnected issue 3) Check Mantis 1611 - Issues after connecting USB mouse => Done 4) Check Mantis 1655 - network jitter and drop test => in progress 5) xTS certification => * xTS self-test on 15.537.8 CTS/CTS-ON-GSI: in progress, there are many media failures, it will cause many timeouts CTS-Verifier: not started VTS/TVTS/STS/GTS/YouTubeTest: done SmokeTest: In Progress, Current new issue: *Can not go to suspend resume 0001651 Based on our plan, we should submit to 3PL yesterday. But we still have CTS media related failures. Please help to check, thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check passive standby issues on ATV12 => in progress, check BT RCU disconnected issue 3) Check Mantis 1655 - network jitter and drop test => Done, add extend received buffer size 4) Check Mantis 1656 - Device was set to speaker instead of hdmi when standby mode => in progress 4) xTS certification => * xTS self-test on 15.537.8 CTS/CTS-ON-GSI: in progress, there are many media failures, it will cause many timeouts. Need patches from AML CTS-Verifier: not started VTS/TVTS/STS/GTS/YouTubeTest: done SmokeTest: In Progress, Current new issue: * Suspend/resume will lose focus (Digicap/SPTEK, 0001586) * Notification not meet requirement (Digicap, 0001609) * App sorting function (Digicap, 0001636) * HotKey will cause system to crash (Digicap, 0001658) * Suspend/Resume fail (Digicap, 0001651) -Wake on Casting random fail *Login SKB account will show the black screen 15.537.8 -Need to change webUI version to dev v534 Based on our plan, we should submit to 3PL already. But we still have CTS media related failures. Please help to check, thank you ! B.R. Kerwin |
|
|
Hi Kerwin Please update the status of Google's test in the document below https://docs.google.com/spreadsheets/d/1OKc7HVUg9ppu6Ie5-svmI-5yQC3w0sZJOq2DBbI_PWg/edit#gid=2051529080 Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check passive standby issues on ATV12 => in progress 3) Correct keycode for BPM-14727 > Done 4) xTS certification => * xTS self-test on 15.537.8 => please check it on Google drive https://docs.google.com/spreadsheets/d/1OKc7HVUg9ppu6Ie5-svmI-5yQC3w0sZJOq2DBbI_PWg/edit#gid=2051529080 * xTS self-test on 15.537.12 => in progress Based on our plan, we should submit to 3PL already. But we still have CTS media related failures. Please help to check, thank you ! B.R. Kerwin |
|
|
Hi Kerwin About CTS media related failures https://jira.skbroadband.com/browse/AMANDROIDS-71 I received a resolved library(2023-02-20_lib.tgz) from AML. ( please apply it to amlogic/common/prebuilt/libstagefrighthw/lib ) Please proceed with the CTS media test with this. If this test result is passed, it will be an official release. Thank you YK.Jung |
|
|
Hi YK, As you know, we are runing xTS self-test on v15.537.12 release. We don't have morel PCs to check AML's patch for those media related fails. Please help to check result from Intek and AML first. Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check passive standby issues on ATV12 => in progress 3) Check Mantis 0001656 => reproduce issue, check it on AML ref. board 4) xTS certification => * xTS self-test on 15.537.12 => in progress GTS 10_R3 will check the if the TrichromeLibrary is prebuilt. With compressed APKs, we will have fail on this item (run gts -m GtsWebViewTestCases -t com.google.android.webview.gts.WebViewTest#testTrichromeLibraryVersionsMatch) Please discuss this with SPTEK in advanced. B.R. Kerwin |
|
|
Hi Kerwin I know that FXN is working hard to support us now. However, if there is a problem with SKB ATV12 Google approval, this situation may be serious. FYI, INTEK/INNOPIA is currently doing whatever it takes to follow SKB's schedule. Regardless of SKB's QA/BMT FW, INTEK will build itself and proceed with ATV12 Google test(Letter upgrade). First of all, after getting ATV12 Google approval, INTEK is planning to get additional Google approval(self test) with FW that completed SKB QA/BMT. It seems that FXN should also consider this method of INTEK. By this week, ATV12 Google Test Final FW should be built and Google Test should be started. (ASAP) Then the 3PL test will be finished next month and FXN can get Google approval. And FXN need to get Google approval(self Test) once again for FW that passes QA/BMT within March FYI,ATV10 also needs to be considered The schedule I am currently expecting is as follows. Please check this schedule. INTEK and INNOPIA just submitted the schedule ending in March to SKB. <ATV12> 2/20 ~ 3/29 : SKB QA/BMT 2/24 ~ 3/02 : FXN ATV12 pre-test 3/03 ~ 3/14 : 3PL Test 3/15 ~ 3/21 : Google review If this FW must be distributed in the field, I will ask SKB manager and QA team to distribute some of it 3/21 ~ 3/28 : FXN pre-test again with almost final FW of QA/BMT (self test) 3/29 ~ : Google review <ATV10> 2/20 ~ 3/17 : SKB QA/BMT 3/13 ~ 3/17 : FXN pre-test 3/20 ~ 3/24 : Google review Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check passive standby issues on ATV12 => fix wake-up by RCU key issue 3) Check Mantis 0001656 => add event to notify, will release a test FW to ALT 4) xTS certification => will update schedule later B.R. Kerwin |
|
|
Hi YK, Regarding the schedule, 2/25 ~ 2/28 is our National Holiday, Our QA office has a scheduled power outage for maintenance. all tests will be postponed. As far as I know, We have 2 other customers who have requested our QA resources in March. Because resources are limited, it is difficult to request QA resources for certain product 3 times in a month. Please adjust your schedule, we can set the highest priority for Smart3 ATV12 LetterUpgrade certification, but the rest of Smart3 certification schedule, I can not guarantee it. >>INTEK will build itself and proceed with ATV12 Google test(Letter upgrade). Please let us know which commit fix the xTS related failure, we MUST include it, please also ask Amlogic to provide correct media library to pass CtsMediaTestCases. if everything goes OK, we will start ATV12 self-built/pretest from 3/1. 3/1-3/7 FXN preTest 3/8-3/17 3PL Test 3/20 ~ Google review (Please remember we have HWC_REAL_MODE issue) Thanks, Jason |
|
|
Hi Jason / Kerwin >>>>INTEK will build itself and proceed with ATV12 Google test(Letter upgrade). >> Please let us know which commit fix the xTS related failure, we MUST include it, please also ask Amlogic to provide correct media library to pass CtsMediaTestCases. The Media library prepared by AML was tested by INTEK, and the result was Fail. AML will find out the cause and update it later today evening. https://jira.skbroadband.com/browse/AMANDROIDS-71 all CEC-related tests should be passed with v15.537.14, which will be released today. And it has already been tested with INNOPIA BOX, and except for one case, all of the results were passed. It is said that one failed item became pass when retried. The fail test information is as follows. android.hdmicec.cts.common.HdmiCecStartupTest#cectVerifyStartupMessages_Cec14b I will adjust the schedule again after checking Thank you YK.Jung |
|
|
HI Jason / Kerwin Then how about this schedule? <ATV12> 2/20 ~ 3/29 : SKB QA/BMT (FIX) 3/01 ~ 3/07 : FXN ATV12 pre-test 3/08 ~ 3/17 : 3PL Test 3/20 ~ 3/24 : Google review If this FW must be distributed in the field, I will ask SKB manager and I think it might be possible to distribute it to some specific user groups. 3/23 ~ 3/29 : FXN pre-test again with almost final FW of QA/BMT (self test) 3/30 ~ : Google review <ATV10> 2/20 ~ 3/17 : SKB QA/BMT (FIX) 3/13 ~ 3/17 : FXN pre-test 3/20 ~ 3/24 : Google review Additionally, ATV10 is no longer available for Google approval after March. Please check it Thank you YK.Jung |
|
|
Hi YK, I've explained that there are 3 Smart3 FW certification within March, it is difficult to request QA resources. The QA team leader thinks it is unreasonable. We have 2 other customers who have already requested our QA resources in March. (They also book a 3PL schedule) Please let us know the priority. ATV12(LetterUpgrade), ATV12(Self-MR), ATV10(Self-MR). We can set the highest priority for Smart3 ATV12 LetterUpgrade certification, but the rest of Smart3 certification schedule, we can not guarantee it. Thanks, Jason |
|
|
Hi Jason The priorities are as follows. ATV12(LetterUpgrade) > ATV10(Self-MR) > ATV12(Self-MR) Please let me know FXN available schedule again. and In the case of ATV10, we have to proceed with self-MR because March is the last Google approval. Thank you YK.Jung |
|
|
Hi YK, <ATV12 LetterUpgrade> We've already set the highest priority for it, please ask Amlogic to provide the stable media library to fix CtsMediaTestCases ASAP. 3/20 ~ 3/29 : SKB QA/BMT (FIX) <--- Is 3/20 typo? 3/01 ~ 3/07 : FXN ATV12 pre-test 3/08 ~ 3/17 : 3PL Test 3/20 ~ 3/24 : Google review <ATV10-SelfMR> You can use your schedule first, but we can NOT guarantee it due to limited QA resource. Please fix the SW version ASAP, because from 3/23, we should use new tool. Now, we don't have resource to test new tools (so we don't know if there is new failure in new tools), we plan to use old tool pass it. 2/20 ~ 3/17 : SKB QA/BMT (FIX) 3/13 ~ 3/17 : FXN pre-test 3/20 ~ 3/24 : Google review <ATV12-SelfMR> You can use your schedule first, but we can NOT guarantee it due to limited QA resource 3/23 ~ 3/29 : FXN pre-test 3/30 ~ : Google review Thanks, Jason |
|
|
Hi Jason Thank you for the update. I will talk about this schedule with the SKB manager. >> 3/20 ~ 3/29 : SKB QA/BMT (FIX) <--- Is 3/20 typo? I typed it wrong. I wrote it correctly below. 2/20 ~ 3/29 : SKB QA/BMT (FIX) Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check passive standby issues on ATV12 => check reason of BT RCU disconnection 3) Check Mantis 0001656 => discuss result with ALT 4) xTS certification => * revert patch of Mantis 0001611 due to CTS fail => Done Based on our plan, please make sure AML release patches of CTS media fail by today. And provide solution of Mantis issues with "xTS certification" category. Thank you ! B.R. Kerwin |
|
|
Hi Kerwin AML-FAE has obtained a library related to CtsMediaTestCases. It is currently undergoing an internal test. It will be shared as soon as it is completed. I checked the xTS certification category, but there seems to be no big issue. Please let me know if there is an issue that blocks Google test. If you don't say anything special, I would like to check the following two issues first. - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1586 ( lost focus issue ) - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1651 ( WakeOnCast issue , not stable ) ... And I know that 2/25 ~ 2/28 is your National Holiday but there will be an official FW release on Feb/28th. Can you build it on the Feb/28th? (FYI, Mar/1st is a national holiday in Korea) Thank You YK.Jung |
|
|
Hi YK, Current, please help to check these 2 issues. - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1586 ( lost focus issue ) - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1651 ( WakeOnCast issue , not stable ) >>Can you build it on the Feb/28th? OK, Peter will support it. BTW, please also remind SKB about "HWC_REAL_MODE" issue. The status of this waiver is still not clear. Thank you ! |
|
|
HI Kerwin - About CtsMediaTestCases CtsMediaTestCases result is Fail with libary released yesterday afternoon. So the updated library was released again in the evening. https://jira.skbroadband.com/browse/AMANDROIDS-71 https://bitbucket.skbroadband.com/projects/AMANDROIDS/repos/vendor-amlogic-common/commits/d97ad9fb8302753bcf8bc56165b7b43e7cb1ecde Please proceed with CtsMediaTestCases using this library. Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check passive standby issues on ATV12 => check reason of BT RCU disconnection 3) Check Mantis 0001656 => will commit to BitBucket today 4) xTS certification => * discuss and reply for Mantis 0001666 Need to provide solution of Mantis issues with "xTS certification" category. Thank you ! B.R. Kerwin |
|
|
Hi Kerwin - About CtsMediaTestCases If an issue occurs during the test, please let us know immediately. INTEK/INNOPIA is also supposed to report issues to AML in real time - About Google Test Except for the two below, there is nothing blocked in the Google test, is it correct ? [0001582] : side effect of HWC_ENABLE_REAL_MODE (wavier) [0001666] : Request to review the issue that app ICON image is not visible in the app list. If there is anything important among the remaining xTS certification items, please give me a reminder first. - About ATV12 Project Schedule do you think FXN pre-test start is possible on March 1st? Thank you YK.Jung |
|
|
Hi Kerwin / Jason About CtsMediaTestCases - INTEK : Passed using tool version 12_r7 - INNOPIA : Passed using tool version 12_r6 / 12_r7 - Amlogic : Passed using tool version 12_r7 Please decide which tool version to use. I think the CtsMediaTestCases will pass no matter what the tool version(12_r6 or 12_r7) is used. About FW build - Please build it by yourself and proceed with the Google test. - As previously discussed, the FW version may use 15.537.14. - I think , this FW is only for Google certification, so it would be okay to force it to be set to perist.sys.skb.mode 1 About issue - 0001582 : side effect of HWC_ENABLE_REAL_MODE ( waiver ) => There is no progress update from SKB/INTEK/INNOPIA. I think , we will have to wait a little longer. - 0001666 : ICON image is not visible in the app list => INTEK / INNOPA are proceeding by sending recording file to 3PL to check. They haven't received feedback yet. - 0001651 : RCU power button function abnormal => SPTEK fixed it about casting issue , I checked and it's working ok , please check it - 0001577 : Digicap cannot simply enable Power/Mute function at login page => please check mantis Despite the complicated situation, the Google test of AT12(LR) must be pass. so please proceed with the Google pre-test as soon as possible. tomorrow is a holiday in Korea, so there will be no updates. Thank you very much for your hard support. YK.Jung innopia_12_r6.PNG (32,093 bytes) INTEK_12_r7.PNG (111,808 bytes) |
|
|
Hi YK, According to our current schedule, 3PL should finished all tests before 3/23. if 3PL can finished it before 3/23. we can use r6 tools. During the 15.537.14 (self built) pre-test, if we encounter any failures, it may lead to the fact that we should rebuild new image and use new tools. At that time, we will remove ZemKid first, and restore Google Webview/TrichromeLibrary due to https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1661 >>About FW build >>- Please build it by yourself and proceed with the Google test. Already built, and released to our QA this morning. >>- As previously discussed, the FW version may use 15.537.14. >>- I think , this FW is only for Google certification, so it would be okay to force it to be set to perist.sys.skb.mode 1 we can set it dynamically, you can refer to Test_env_v1.xlsx in mantis#1666 Thanks, Jason Foxconn_12_r7.png (38,434 bytes) |
|
|
Hi Jason Previously, I asked Amlogic to proceed with the CtsMediaTestCases using the 12_r6 version. I just received the results. strangely, four test failures were observed in relation to the volume side. This Amlogic test was not conducted by a professional tester so it is not clear whether this fail items are normal or not. so if you are planning to use 12_r6 now, it would be better to check these 4 fail cases in advance. Thank you YK.Jung Amlogic_12_r6_result.PNG (164,987 bytes) |
|
|
Hi YK, the 4 cases you mentioned are pass on our side. Test FW: 15.537.14 (Self-build) Test tool: cts 12_r6 Thanks, Jason testVolumeKey_afterSessionReleased.jpg (244,068 bytes) testCallbacksAreCalledWhenVolumeChanged.jpg (219,434 bytes) testRouteCallbackOnRoutesChanged_whenLocalVolumeChanged.jpg (232,949 bytes) |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check Mantis 0001667 - STB box enters passive standby mode ( sleep <-> wakeup ) => in progress 3) Check Mantis 0001613 - Free space shown as 0B when inserting USB Stick(FAT32) => in progress 4) xTS certification => doing xTS pre-test on v15.537.14 Please check standby/resume function with SPTEK ( Mantis 0001651 RCU power button function abnormal) Thank you ! B.R. Kerwin |
|
|
Hi Jason / Kerwin After applying the updated SPTEK's patch late last evening, the casting issue has not been observed yet. It seems more stable to apply the new patch. we will test it a little more until the morning. And If FXN rebuild it today and proceed with the Google test, Please let me know the overall schedule about ATV12 LetterUpgrade / ATV10-SelfMR / ATV12-SelfMR Thank you YK.Jung |
|
|
Hi YK, 15.537.14 Only CTS/CTS-ON-GSI/SmokeTest is not yet complete. We will suspend 15.537.14 when the 15.537.16 is released 15.537.16 = 15.537.14 + 2 framework/base patch (wake On Casting) We will start test from this evening. Please also check casting issue on your side, If it won't be better than 15.537.14. I think we can use 15.537.14 to finish the rest of test suite. <ATV12 LetterUpgrade> We've already set the highest priority for it, please also check the SPTEK's patch stability on your side. 2/20 ~ 3/29 : SKB QA/BMT (FIX) 3/03 ~ 3/09 : FXN ATV12 pre-test (15.537.16) 3/10 ~ 3/21 : 3PL Test 3/20 ~ 3/24 : Google review The following schedule is no change. <ATV10-SelfMR> You can use your schedule first, but we can NOT guarantee it due to limited QA resource. Please fix the SW version ASAP, because from 3/23, we should use new tool. Now, we don't have resource to test new tools (so we don't know if there is new failure in new tools), we plan to use old tool pass it. 2/20 ~ 3/17 : SKB QA/BMT (FIX) 3/13 ~ 3/17 : FXN pre-test 3/20 ~ 3/24 : Google review <ATV12-SelfMR> You can use your schedule first, but we can NOT guarantee it due to limited QA resource 3/23 ~ 3/29 : FXN pre-test 3/30 ~ : Google review Thanks, Jason |
|
|
Hi Jason No issue has been observed so far in SPTEK's final patch yesterday. And even if FW is rebuilt and tested, there is no big difference in the schedule. Therefore, please proceed with the Google test with v15.534.16 when you are ready. And please share it when the FW(v15.534.16) is built. Thank you YK.Jung |
|
|
Hi YK, 15.537.16 (Self-build) SU https://drive.google.com/file/d/18MY4PBLJ52HT5YAbGtT6JEKCBf3zxSLY/view?usp=share_link SD https://drive.google.com/file/d/1VXHujY7alaajBkeROdbDSTen3t9AjK8c/view?usp=share_link Thanks, Jason |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check Mantis 0001667 - STB box enters passive standby mode ( sleep <-> wakeup ) => in progress 3) Check Mantis 0001613 - Free space shown as 0B when inserting USB Stick(FAT32) => in progress 4) Check Mantis 0001671 - sometimes NUGU doesn't work well => in progress 5) xTS certification => doing xTS pre-test on v15.537.16 => re-build FW with 'wakeup on cast' patches and do xTS pre-test Thank you ! B.R. Kerwin |
|
|
Hi YK, Update current status for ATV12 OS development 1) Check Mantis 1610-MIC does not work in karaoke app => pending, wait for AML Korea's response 2) Check Mantis 1667 - STB box enters passive standby mode ( sleep <-> wakeup ) => check for patch (https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1667#c12421) 3) Check Mantis 0001613 - Free space shown as 0B when inserting USB Stick(FAT32) => It will be OK if we use ATV10 Android's implementation in Framework. 4) Check Mantis 0001671 - sometimes NUGU doesn't work well => in progress 5) xTS certification => doing xTS pre-test on v15.537.16 CTS/GSI/SmokeTest: InProgress VTS/STS/GTS/TVTS/YouTube: Done Thank you ! B.R. Kerwin |
|
|
Hi Kerwin BMT is in progress for ATV10 / ATV12. We need to check with the following issues quickly. 1) There is an issue when FXN compress apk now. how can we solve the lack of space? YouTube kids app should be included in FW zemkids update should be successful - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1555 - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1661 2) passive standby issues (STB enters passive standby mode during test with TV) - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1586 - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1667 3) NUGU issue - https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1671 Thank you!! YK.Jung |
|
|
Hi YK, 1) Storage issue We are checking if it is OK to not include files for ringtone. If these files are needed for xTS, then we don't have other solution except to do compressing in Zemkid APP or to use PAI for YouTubeKids. 2) passive standby issue => under testing, will commit to BitBucket if no other issue is found. 3) NUGU issue => a timing issue, under verification BTW, current xTS pre-test status for ATV12 is SmokeTest: InProgress CTS/CTS-ON-GSI/GSI/VTS/STS/GTS/TVTS/YouTube/BTS: Done Thank you ! |
|
|
Hi YK, Is there any update for 'HWC_ENABLE_REAL_MODE ' waiver from SKB/Google ? (Mantis 0001582 : side effect of HWC_ENABLE_REAL_MODE) xTS pre-test is going to be finished, we need to know if it is OK to sumbit to 3PL. Please let us know the result. Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Storage issue Build is OK after removing some sound effect files. (Zemkids is not compressed, YouTubeKids is also included) We are going to run CTS test to check if there is any side effect. 2) passive standby issue => Done, commit to BitBucket today 3) NUGU issue => a timing issue, review solution and do more tests 4) xTS certification Current xTS pre-test of ATV12 is almost done. We are preparing document for 3PL submission. SmokeTest: almost done CTS/CTS-ON-GSI/GSI/VTS/STS/GTS/TVTS/YouTube/BTS: Done Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Storage issue Commit to BitBucket already, running CTS test to check if there is any side effect. 2) NUGU issue => a timing issue, review solution and do more tests 3) Check log of Mantis 0001673 for TV compatibility issue => in progress 4) xTS certification Submit to 3PL on 3/9 Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) NUGU issue => a timing issue, review solution and do more tests 2) Check log of Mantis 0001673 for TV compatibility issue => please check reply on Mantis and discuss with SPTEK 3) Mantis#1676 for FW downgrading with lower security patch level => build and provide test FW to ALT 4) xTS certification => already submit to 3PL on 3/9. Help 3PL to do FW update on ATV12 Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1678 sleep mode upgrade issue => in progress 2) NUGU issue => commit to BitBucket, wait for ALT test result to close 3) Check Mantis#1677 issue for hdmi_edid.xml file => in progress 4) xTS certification => wait for 3PL updates Thank you ! |
|
|
Hi kerwin , jason AML issue was observed on ATV10 FW(v15.536.16), which was requested to build yesterday. So it hasn't been decided whether to proceed with Google with this FW. The final ATV10 FW has not been decided yet, so I haven't sent an official Google pre-test mail yet. and due to this, the google schedule delay is currently occurring, and I reported this delayed situation to SKB. SKB manager is planning to build again the final ATV10 FW on Thursday(3/16) When the final FW is decided, I will send you an official Google pre-test email. Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1678 sleep mode upgrade issue => done, will commit to BitBucket for ATV10/ATV12 2) Mantis#1671 for NUGU issue => done 3) Check Mantis#1677 issue for hdmi_edid.xml file => done 4) xTS certification => wait for 3PL updates BTW, please check Mantis#1673, 0001676 and reply results Thank you ! |
|
|
Hi Kerwin / Jason Currently, the observed AML issue is being treated as a minor issue. SKB wants to finish with the current FW if no more critical issues are found. So SKB was asked me to proceed with Google pre-test with the existing FW(v15.536.16) so I sent you an official pre-test email Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => check log from ALT 2) Check Mantis#1667 issue for standby issue => reply on Mantis 3) Check log for Mantis 0001610 MIC issue => reply on Mantis 4) xTS certification => wait for 3PL updates BTW, please discuss Mantis#1661 with SKB/SPTEK/Intek We can't use compressed APK for Webview and TrichromeLibrary due to CTS tool change. There is no enough storage space on Eagle. Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => check log from ALT 2) Check Mantis#1667 issue for standby issue => reply on Mantis 3) Check log for Mantis 0001681 BT RCU issue => reply on Mantis 4) xTS certification => wait for 3PL updates BTW, please discuss Mantis#1661 with SKB/SPTEK/Intek We can't use compressed APK for Webview and TrichromeLibrary due to CTS tool change. There is no enough storage space on Eagle. Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => try to reproduce issue 2) Check Mantis#1667 issue for standby issue => add a check for CTS, committed to BitBucket 3) xTS certification => work with 3PL to run xTS test cases Thank you ! |
|
|
Hi Kerwin * ATV12 LR wavier ( TVTS and CTS-V ) - Waiver is currently discussing between Google and INTEK/AML (in progress) * ATV12's self-MR FW also needs to be prepared for the BMT/QA end - free space issue YouTube kids is not included yet. Webview / Trichrome Library must also be uncompressed How can we solve this issue? and please let me know if you have any suggestions for SKB. Please let me know approximately how much free space we need now. - Nugu issue This issue is a serious situation. https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1671 Please check it quickly. Thank you YK.Jung |
|
|
Hi YK, 1. YouTube kids is already included for a while. Please double check. 2. Webview / Trichrome Library must also be uncompressed => We already highlight this issue before, the only possible solution seems to use compression on SPTEK's Webview/Trichromelibrary. We also provide a SOP to do compressed APK in Mantis#1614. - Nugu issue => From the video, ALT isdoing stress test on NUGU function. If NUGU works well under usuall case, I think it is not a serious issue. Thank you ! |
|
|
Hi Jason Now Google is asking SKB for information about the waiver TVTS / CTS-V. so each manufacturer have to provide SKB with the following information. 1) (waiver) Issue tracer information(or link) received when reporting to 3PL 2) FW(self-build v15.537.16)'s fingerprint submitted to 3PL Please let me know these two information Thank you YK.Jung |
|
|
Hi YK, 1) https://issuetracker.google.com/269342225 2) SKB/BFX_AT100/BFX-AT100:12/STTC.220724.001/15.537.16-20230303:user/release-keys The build is under testing, our 3PL hasn't submited all reports to Google System. Thanks, Jason |
|
|
Hi Jason The meeting with SKB is over now. Currently, two major issues have been reported in UI536. 1) BA01 pairing issue https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1680 https://jira.skbroadband.com/browse/BPM-15728 2) UI536 slow compared to 535 when measuring warm boot speed https://jira.skbroadband.com/browse/BPM-15728 The final UI536 FW for Google test will be built only after these two issues are resolved. and I have already reported the delay in UI536 Google schedule to SKB. Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => still can't reproduce issue, will add debug messages and need ALT's help to get log 2) Check Mantis#1613/1616 issue => committed to BitBucket 3) xTS certification => 3PL is going to finish xTS tests. Is there any update for 'HWC_ENABLE_REAL_MODE ' waiver from SKB/Google ? Thank you ! |
|
|
Hi YK, Our 3PL has finished the test, (1 CTS-V fail and 32 TVTS fail) if Google ask SKB to provide the following information, I think SKB can forward it. fingerprint: SKB/BFX_AT100/BFX-AT100:12/STTC.220724.001/15.537.16-20230303:user/release-keys APA link: https://partner.android.com/approvals/builds/devices-8FDA301E-products-41F5E53D-builds-73E6293F/overview/build-meta Thanks, Jason |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => still can't reproduce issue, please help to check if issue still exists on v15.537.281. There is a patch from AML. 2) Check Mantis#1661 - testTrichromeLibraryVersionsMatch => verify on Intek's box 3) Check Mantis#1684 - HDR error when HDMI reconnect => pick patch from ATV10 and verify 4) xTS certification => 3PL finishes xTS tests and submits to Google. Is there any update for 'HWC_ENABLE_REAL_MODE ' waiver from SKB/Google ? Thank you ! |
|
|
HI Kerwin, Jason * About ATV12 waiver There are still no updates. - Google and INTEK/AML are discussing this waiver - Additionally, AML is planning a patch to fix this issue. (This patch is expected to take a long time) * About ATV10 self-MR ATV10(UI536) FW for Google self-MR is not ready yet. Due to the current schedule, even if it is built now, Google approval cannot be obtained within March according to the previous SKB schedule. Therefore, the Google approval of ATV10 will be delayed to April. (Previously, SKB and Google discussed ATV10 until March, this issue which is delayed to April has to be resolved by SKB ) Anyway , we need to prepare for the delay of ATV10(UI536) to April. If there is a patch that needs to be applied in ATV10, please apply it in advance ( for example security patch , GTVS update ) ATV10's final FW is almost ready and the final FW could be built soon Thank you! YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => add more debug messages, check log from ALT 2) Check Mantis#1687 - Ethernet issue after cold boot => in progress, try to reproduce and check log 3) Check Mantis#1689 - free space => in progress, build and check result 4) Check Mantis#1684 - HDR error when HDMI reconnect => done 5) xTS certification => 3PL finishes xTS tests and submits to Google. no updates so far Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => checking another log from ALT 2) Check Mantis#1687 - Ethernet issue after cold boot => try to reproduce and check log 3) Check Mantis#1689 - free space => re-build FW and check result 4) xTS certification => 3PL finishes xTS tests and submits to Google. no updates so far Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => need ALT's help to get log again 2) Check Mantis#1687 - Ethernet issue after cold boot => reproduced and check log 3) Check Mantis#1689 - free space => It's OK after remove YouTube and AppleTvPlus app without compression for WebView/TriChromeLibrary 4) xTS certification => 3PL finishes xTS tests and submits to Google. no updates so far Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => in progress, check log 2) Check Mantis#1687 - Ethernet issue after cold boot => reproduced and check log 3) Check Mantis#1689 - free space => will update test result on Mantis 4) xTS certification => 3PL finishes xTS tests and submits to Google. no updates so far Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis#1671 for NUGU issue => in progress, check log 2) Check Mantis#1687 - Ethernet issue after cold boot => reproduced and check log 3) Check Mantis#1689 - free space => update test result on Mantis 4) Mantis 0001694 for YouTubeKids PAI => discuss on Mantis 5) xTS certification => 3PL finishes xTS tests and submits to Google. no updates so far Thank you ! |
|
|
Hi Kerwin - About ATV12 waiver issue AML is working on this issue, and AML will solve it by 4/14. - About ATV12 Major issues 1) nugu issue https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1671 2) BA01 pairing issue https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1702 3) free space issue https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1699 https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1694 https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1689 - About ATV10 self-MR Please let me know the schedule of self-MR for ATV10(v15.536.26) version. Thank you!! YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1687: Network issue after LAN connection after cold boot ==> provide a test FW to ALT on 3/31, wait for ALT's feedback 2) Mantis-1671: NUGU voice recognition does not work ==> check for ALT's reply 3) Mantis-1699: install apps automatically that are not included in FW ==> check for solutions 4) Mantis-1702: BA01 RCU pairing issue ==> try to reproduce ( 6/30 pairing fails, with latest code base on BitBucket) Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1687: Network issue after LAN connection after cold boot ==> pending, wait for SPTEK's reply 2) Mantis-1671: NUGU voice recognition does not work ==> will build a test FW to ALT 3) Mantis-1699: install apps automatically that are not included in FW ==> please check reply on Mantis 4) Mantis-1702: BA01 RCU pairing issue ==> please check reply on Mantis, now it is 3/30 fails which is better than before Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1687: Network issue after LAN connection after cold boot ==> pending, wait for SPTEK's reply 2) Mantis-1671: NUGU voice recognition does not work ==> check for patch on AOSP git 3) Mantis-1699: install apps automatically that are not included in FW ==> wait for ALT's feedback 4) Mantis-1702: BA01 RCU pairing issue ==> please update test result Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1687: Network issue after LAN connection after cold boot ==> pending, wait for SPTEK's reply 2) Mantis-1671: NUGU voice recognition does not work ==> check log about GATT service 3) Mantis-1582: HWC_REAL_MODE issue ==> apply patch from AML and build FW 4) Mantis-1702: BA01 RCU pairing issue ==> Is it OK to commit changes ? Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1687: Network issue after LAN connection after cold boot ==> done, commit to BitBucket 2) Mantis-1671: NUGU voice recognition does not work ==> check log updated on 0414 3) Mantis-1582: HWC_REAL_MODE issue ==> apply patch from AML, result was updated on Mantis. Please check fail with AMLogic 4) Mantis-1702: BA01 RCU pairing issue ==> done, commit to BitBucket Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1671: NUGU voice recognition does not work ==> check log updated on 0417 2) Mantis-1582: HWC_REAL_MODE issue ==> doing xTS verifications. 3) Do Amazon Prime Video self-test ==> in progress Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1671: NUGU voice recognition does not work ==> Done, will commit to BitBucket 2) Mantis-1582: HWC_REAL_MODE issue ==> doing xTS verifications. 3) Do Amazon Prime Video self-test ==> in progress, plan to finish 1st round tests on 4/28 4) Mantis 0001709 - Screen is not on after doing upgrade in sleep mode ==> check logs Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1671: NUGU voice recognition does not work ==> check another log uploaded today 2) Mantis-1582: HWC_REAL_MODE issue ==> doing xTS verifications. CTS-V/STS: Done, GSI/TVTS: Retrying 3) Do Amazon Prime Video self-test ==> in progress, plan to finish 1st cycle test on 4/28 4) Mantis 1709 - Screen is not on after doing upgrade in sleep mode ==> check logs Thank you ! |
|
|
Hi Jason About the test results after applying HWC_ENABLE_REAL_MODE patch (https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1582) AML says it will solve the Google Test Fail item by April 26th. If so, I think you can check if it's actually resolved by April 28th. Please let me know the estimated schedule for starting the Google test ATV12(LR) from the beginning of May. (Google approval will proceed regardless of SKB BMT) Thank you YK.Jung |
|
|
Hi YK, The 5/1 is our national holiday, and Please let us know the priority of SKB request. These 2 products have been on the market for many years, our QA leader can not put more resource on it. Sometimes, our QA also need to accepted unexpected test request for verifying Amlogic Patch, Please also consider it. ATV12 certification ATV10 of Eagle hot fix (You informed us yesterday) ATV10 of Swan pretest, currently, we are testing it. Amazon Prime Video for ATV12 Eagle. Thanks, Jason |
|
|
Hi Jason There is no distribution schedule for ATV10 yet. ( so ATV10 is low priority now ) Please let me know the schedule for the two cases below. 1) AISoundMAX > ATV12(LR) > ATV10 > Amazon Prime Video for ATV12 Eagle 2) ATV12(LR) > AISoundMAX > ATV10 > Amazon Prime Video for ATV12 Eagle ( Please assume that ATV12 (LR) will start after May 2nd ) Thanks YK.Jung |
|
|
Hi YK, >>1) AISoundMAX > ATV12(LR) > ATV10 > Amazon Prime Video for ATV12 Eagle I don't know the release plan of SWAN, so I don't know how to estimate it. >>2) ATV12(LR) > AISoundMAX > ATV10 > Amazon Prime Video for ATV12 Eagle From 5/2, (5 working days) -> 3PL (8 working days) Thanks, Jason |
|
|
Hi Jason About AISoundMAX SKB QA : ~ 5/3th : Final FW will be confirmed on May/3th, FXN can pre-test start after May/3th About Smart3 - ATV10 of Eagle hot fix : Exclude from Schedule (Ignore) - ATV12(LR) :Proceed regardless of SKB QA. (Proceed after FXN self build.) That is , proceed as soon as the FW to be approved by Google is ready (The current test result of INTEK seems to be no issue now, and Google pre-test will be conducted after build early next week.) - ATV12(self-MR): The schedule for SKB QA has not been released yet, but it is expected to be confirmed before May/17th. SKB manager is requesting Google approval by June/5th. About Amazon Prime Video - lowest priority Please give me the schedule when proceeding with the priority below with the above information. 1) ATV12(LR) > AISoundMAX > ATV12(self-MR) > Amazon Prime 2) AISoundMAX > ATV12(LR) > ATV12(self-MR) > Amazon Prime Thank you YK.Jung |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1671: NUGU voice recognition does not work ==> monitor, patch is committed to BitBucket 2) Mantis-1582: HWC_REAL_MODE issue ==> check CtsGraphicsTestCases failures 3) Do Amazon Prime Video self-test ==> pending due to priority is lower than ATV12 google certification 4) Mantis 1513 - No audio in NUGU / Google assistant when enable passthrough mode ==> commit to BitBucket Thank you ! |
|
|
Hi YK, >>Please give me the schedule when proceeding with the priority below with the above information. >>1) ATV12(LR) > AISoundMAX > ATV12(self-MR) > Amazon Prime >>2) AISoundMAX > ATV12(LR) > ATV12(self-MR) > Amazon Prime I've checked the schedule with Wooshin, He said the AISoundMax is more important than ATV12(LR self build) As far as I know, there will be at least one SWAN official release next week, After our QA get SW image and SKB request, we will start SWAN pretest, if everything goes well and there is no critical issue during BMT, we'll submit SWAN first. If we have idle PCs, we can run Smart 3 auto test in parallel. Thanks, Jason |
|
|
Hi Jason If FXN does Google test in parallel, there will be no issue in the schedule. Anyway I have to report the schedule to SKB . Please proceed with Google test as soon as self-build FW is ready. I think FXN should start the Google test at least from April 26th Please let me know the estimated Google schedule of ATV12 LR. ( including days off ) ATV12 LR pre-TEST : (?) 3PL TEST : (?) Google reivew : (?) ATV12 MR (My expected schedule is as follows) pre-Test : 5/24 ~ 5/30 Google reivew : 5/30 ~ 6/05 Thank you YK.Jung |
|
|
Hi YK, >>If FXN does Google test in parallel, there will be no issue in the schedule. Only auto test suite can be run in parallel if we have idle PCs According to your schedule, I will start to integrate Smart3 self-build next Mon. Our QA will start test Smart3/AISoundMax next week, but if they need to test manual test (the Swan will be first priority, they will pause manual test of Smart3) so the working days of Smart3 pretest will not be 5 on FXN side. pre-TEST : 4/26, ~ ? (maybe 8 working days, because the manual test will be delay) 3PL TEST : I need to check it with 3PL. because SKB submit 2 models at the same time, I think we also need to let 3PL know the priority Google reivew : (?) Thanks Jason |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1671: NUGU voice recognition does not work ==> monitor, patch is committed to BitBucket 2) Mantis-1582: HWC_REAL_MODE issue ==> fix CtsGraphicsTestCases fail, wait for AML patch 3) Do Amazon Prime Video self-test ==> pending due to priority is lower than ATV12 google certification 4) Mantis 1709 - screen is not on after upgrading under sleep mode ==> release a test FW to ALT Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1671: NUGU voice recognition does not work ==> closed 2) Mantis-1582: HWC_REAL_MODE issue ==> integrate AML patch and build a FW to run xTS self-tests 3) Do Amazon Prime Video self-test ==> in progress, priority is lower than xTS 4) Mantis 1709 - screen is not on after upgrading under sleep mode ==> done, commit to BitBucket Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> study document 2) Mantis-1582: HWC_REAL_MODE issue ==> in progress, run xTS self-tests 3) Do Amazon Prime Video self-test ==> in progress, priority is lower than xTS (finish 80%) 4) Mantis 1555 - check update fail after ZemKids is compressed by GZIP ==> done, version code is needed to update as well Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1582: HWC_REAL_MODE issue for Google certification ==> GTS/VTS/CTS-V/STS done, others are in progress, plan to finish on 5/3 Please help to check "empty icon" issue on all APPs page with SKB. Jason had sent picture to you for this issue. 2) Do Amazon Prime Video self-test ==> in progress, priority is lower than xTS (finish 82%) 3) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> study document and check BTF API for implementation Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1582: HWC_REAL_MODE issue for Google certification ==> GTS/VTS/CTS-V/STS/GSI done, others are in progress, plan to finish on 5/3 2) Do Amazon Prime Video self-test ==> in progress, priority is lower than xTS (finish 85%) 3) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> implement API changes Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1582: HWC_REAL_MODE issue for Google certification ==> monitor, submit to 3PL on 5/4 2) Do Amazon Prime Video self-test ==> check with AML to solve 4 fail items 3) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> in progress, implement API changes 4) Mantis1715: new apps installed by PAI ==> in progress, testing Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis1709: The screen is not showing when press power key while sleep mode upgrade ==> check log and replied comments to ALT 2) Do Amazon Prime Video self-test ==> check with AML to solve 4 fail items 3) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> in progress, check resolution change fails 4) Mantis1715: new apps installed by PAI ==> in progress, check config Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis1709: The screen is not showing when press power key while sleep mode upgrade ==> modify and build a test FW to ALT 2) Do Amazon Prime Video self-test ==> check with AML to solve 4 fail items 3) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> in progress, need to check how to sync with Framework API 4) Mantis1715: new apps installed by PAI ==> monitor 5) Mantis1714: backup and restore BT pairing config for OS downgrade ==> under FXN internal discussion Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis1709: The screen is not showing when press power key while sleep mode upgrade ==> wait for ALT test result 2) Do Amazon Prime Video self-test ==> create JIRA issue on Amazon for discussion of 4 fail items 3) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> in progress, need to study how to call Framework API from BTF API(native C++) 4) Mantis1714: backup and restore BT pairing config for OS downgrade ==> under FXN internal discussion Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis1709: The screen is not showing when press power key while sleep mode upgrade ==> closed 2) Do Amazon Prime Video self-test ==> discuss JIRA issue with Amazon/AML for of 3 fail items 3) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> in progress, try to set resolution by Google Framework API 4) Mantis1714: backup and restore BT pairing config for OS downgrade ==> checking ALT's comments Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Do Amazon Prime Video self-test ==> discuss JIRA issue with Amazon/AML for of 3 fail items 2) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> in progress, try to set resolution by Google Framework API 3) Mantis1714: backup and restore BT pairing config for OS downgrade ==> checking ALT's comments 4) Mantis1723: EDID issue after STB sleep -> wake up ==> check and build a test FW Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> in progress, test BTF API with different TVs 2) Check with 3PL on xTS fail item (CtsHostsideNetworkTests) 3) Mantis1723: EDID issue after STB sleep -> wake up ==> wait for ALT test result Thank you ! |
|
|
Hi YK, Update current status for ATV12 OS development 1) Mantis-1711: Request for implementation of resolution change for HWC_REAL_MODE ==> in progress, integrate AML and Digicap UI for resolution change 2) Check with 3PL on xTS fail item (CtsHostsideNetworkTests) ==> 3PL submit to Google today 3) Mantis1723: EDID issue after STB sleep -> wake up ==> check ALT test log 4) Do Amazon Prime Video self-test ==> discuss JIRA issue with Amazon/AML for of 1 fail item Thank you ! |
|
|
Hi Kerwin , Jason ATV12 BMT is currently in progress with v15.537.48 And ATV12 LR BMT Schedule is SKB BMT: Working day is 10 days from May 29th And there will be a Smart3 FW release this Friday(June 2nd). (Almost final FW) Before that, please apply what you need to commit. In addition, please let me know in advance if there are any issues among Google items. Thank you YK.Jung |
|
|
Hi YK, Current, there is a new fail in GTS 10_R4. We've reported to AML FAE and got patch. Becasue GTS retry is still in progress, we are not sure if the patch is OK or not. ( run gts -m GtsMediaTestCases -t com.google.android.media.gts.WidevineVP9WebMPlaybackTests#testVP9WebMCencSubSampleL3With720P60 ) Thank you! |
|
|
Hi YK, There are 2 potential risks 1. Should we apply 2023-05 Security Patch? if BMT/self-test can be finished within June, I think we can keep current security patch 2023-04. 2. There is a new failures (testVP9WebMCencSubSampleL3With720P60) in GTS10_R4 , required date is June/22, we've reported this failure to Amlogic FAE, he said this is common issue, Amlogic is fixing it, if BMT/self test can be finished before June/22, I think it's not critical issue now. Thanks, Jason |
|
|
Hi Kerwin , Jason ATV12 LR Google approval has already been completed. Therefore, I will close this ticket. Thank you very much for your help. Thanks YK.Jung |
- yk.jung ( (ALTech) Younkwang Jung ) developer
